Technology Stocks | TAVA Technologies (TAVA-NASDAQ)


Previous 10 | Next 10 
To: James Strauss who wrote (19932)7/2/1998 2:12:00 PM
From: John Mansfield   of 31646
 
'...Not many organizations are at the point where they are ready to remedy embedded systems, since they are still scouring through software code. But it is a necessary step in the Y2K compliance process for a corporation. "If facilities can't function--fax machines, LANs which interface to WANs--if those things don't work, then communication is impacted and it becomes the infrastructure that cripples the organization," Daniel says.
....

zdnet.com 

Share Recommend | Keep | Reply | Mark as Last Read

To: James Strauss who wrote (19932)7/2/1998 2:14:00 PM
From: John Mansfield   of 31646
 
'the real ticking time bombs'

'But he's not, mostly because there are so many things that are out of his control: specifically, the embedded chips that reside within mainframes, servers, power grids and telephone circuit switches, to name a few.

These embedded microprocessors, Neuzil would argue, are the real ticking time bombs, not the software programs. "The embedded chips are made from different manufacturers around the world," says Neuzil, senior vice president of the Production Systems Division at The Options Clearing Corp., in Chicago. "We don't know where they are coming from, and we can't look at the code on the chip."

As a result, the first shot of even knowing where these microchip land mines lie in an organization will come on Jan. 1, 2000. Therefore, OCC has lined up two disaster recovery sites, the company is accepting power feeds from two separate grids, and it is buying digital cell phones that double as walkie-talkies. . .
...

zdnet.com 

Share Recommend | Keep | Reply | Mark as Last Read | Read Replies (1)

To: Starfish* who wrote (19933)7/2/1998 2:17:00 PM
From: Ken Salaets   of 31646
 
Updated short interest on TAVA:

viwes.com 

Share Recommend | Keep | Reply | Mark as Last Read | Read Replies (2)

To: Ken Salaets who wrote (19938)7/2/1998 4:36:00 PM
From: Judith Weintraub   of 31646
 
Are the shorts from this past week included in the the 500+ number and what about the damn market- makers.

Share Recommend | Keep | Reply | Mark as Last Read | Read Replies (1)

To: John Mansfield who wrote (19937)7/2/1998 4:38:00 PM
From: paul boudreau   of 31646
 
This is a report from a engineer who attended the ERPI Y2K conf.

SUBJECT Trip Report: EPRI Y2K 98 Conference on Embedded Systems

The EPRI Y2K Embedded Systems Conference in Dallas Texas, held between 5/4/98 to 5/7/98, was divided into different sections/groups. One was tailored to the technical/testing aspects with respect to the Y2K issue, while the second was geared towards the Project Management aspects which included the legal/litigation exposure. This trip report highlights the events of the technical discussions.

SUMMARY

The conference yielded several insights into the Y2K problems facing xxxxxx. It also allowed for "bench-marking" our progress against the rest of the industry. Via a show of hands at the conference, xxxxxx would rank at approximately the 33rd percentile with respect to Y2K awareness, analysis of installed components and the resultant required testing. Some industry leaders (with a large staff dedicated to the Y2K project) are 70% complete with their Y2K embedded issues. The initial good news is that no major modifications have been recognized, to date, stemming from actual Y2K testing. That is not to say there haven't been problems, see EQUIPMENT TESTING below, that required resolution to avoid a possible plant trip due to Y2K issues. It was also obvious that the consensus of the participants do not believe the majority of the original equipment manufactures are going to be forthwith with Y2K related issues due to the possible litigation ramification. It is therefore imperative that xxxxxxx utilize the EPRI database and the resultant industry contacts so as to avert any unforeseen Y2K "glitches". Utilization of the EPRI database may also corroborate that we exercised due diligence with respect to Y2K issues.

REGULATORY ISSUES

It was a consensus of many at the conference that all nuclear power plants will be required to be Y2K compliant/ready by July 1, 1999. This was confirmed by the issuance of NRC Generic Letter 98-01: "Year 2000 Readiness of Computer Systems at Nuclear Power Plants" dated May 11, 1998.

The NRC has adopted the following definitions as they relate to the Y2K issue.

ú "Y2K compliant" is defined as computer systems or applications that accurately process date/time data (including but not limited to calculating, comparing, and sequencing) from, into, and between the 20th and 21st centuries, the years 1999 and 2000, and leap-year calculations.

ú "Y2K ready" is defined as a computer system or application that has been determined to be suitable for continued use into the year 2000 even though the computer system or application is not fully Y2K compliant.

The NCR has also "strongly encourage licensees to share information regarding identified remediation and implementation activities in order to maintain the likelihood that all Y2K problems are identified". Supporting the EPRI database could be viewed as fulfilling this recommendation.

The majority also believed that there will be a Y2K NRC inspection team in place by the fall of 1998, and that ten industry leading plants will be audited as a baseline for future audits.

BACKGROUND

EPRI's Year 2000 Program for Embedded Systems complements efforts to address software-related problems. The program acts as a forum and source of practical information to meet pressing needs for energy providers. This collaborative, noncompetitive program - open to all parties able and willing to share data - consists of four major "components."

1. An electronic system for real-time data and information sharing.

2. Facilitated workshops for interactive discussion of methods and results.

3. Industry wide teams for collaborative development of critical information.

4. R&D for embedded systems.

It should be noted that the embedded system review can not address the higher level software issues which are, by default, client specific.

EPRI's Year 2000 Program is designed to reduce our exposure to Year 2000 problems by increasing the efficiency and cost-effectiveness of our in-house compliance efforts. The program's information and experiences will help xxxxxxx:

1. Identify potentially vulnerable systems, components, and interdependencies and prioritize them by building on the work from other utilities.

2. Prioritize, develop, and implement compliance testing programs utilizing the experience and lessons learned by others, not just from electric utilities.

3. Communicate with, and receive technical assistance from, system and component suppliers and vendors in a cost-effective manner.

4. Exploit approaches successfully applied elsewhere while avoiding duplication and dead-ends.

5. Gather Year 2000 compliance information from key suppliers, vendors, and customers.

6. Support due diligence in Year 2000 preparation for reporting to the financial and regulatory communities.

7. Develop contingency plans and mitigation strategies in anticipation of potential failures occurring both within and outside of our control.

STATUS OF EPRI DATABASE

Several utilities are beginning to enter their Y2K inventory into the EPRI database. A few utilities are entering preliminary test data into the database. Many utilities are only starting their testing program.

The slowness of access to the database has been fixed by EPRI whereas they have installed a new sever for database access over the WEB. The usefulness of the database cannot be realized until the utility participants begin to enter data into the database. The major hurdle, that must be overcome, is legal in nature not technical. Most vendors and several utilities are preparing a universal disclaimer to all data given to the EPRI database to forestall any future litigation due to erroneous postings/information.

EQUIPMENT TESTING

Several utilities have begun their testing of Y2K related system components. Less than a handful are well on in this phase (Palo Verde ~ 70% complete). The good news here is that Palo Verde has yet to hit a "show stopper". They were cautious to specify that the first systems tested were the "low hanging fruit".

Group Consensus (in no order nor priority)

ú The Y2K test teams should be dedicated to the project to ensure timely implementation is realized is met.

ú Most utilities are using the GM test procedure as a skeleton for their own procedures.

ú Software is available to scan most types of software for date related entries.

ú Apparently no one is tracking the individual chips (model\serial numbers) on their equipment containing integrated circuits.

ú Testing must begin as soon as possible so that there is enough time to implement a fix or work around prior to the year 2000.

ú System engineers should shoulder the responsibility and the accountability for all Y2K testing of their systems.

ú It is apparent that the original equipment manufacturers (OEMs) are not accepting responsibility for any testing related to Y2K due to liability concerns. One large OEM will not even review the clients test procedures.

ú An expert from Dallas Semiconductor argued that the "best bet" to beat the Y2K bug is to perform system integrated testing.

ú Most utilities which have begun actual plant or bench testing feel that the vendors of the applicable equipment are on the same learning curve as they are.

ú Actual Test Results (results were given by utilities without reference, due to litigation concerns)

ú Utility UU tested the Westinghouse Inadequate Core Cooling Monitor (ICCM) which failed in the rollover and would have placed their unit in a T/S action statement.

ú Utility VV tested the Bailey INFI-90 system which locked-up partial control during the 2000 rollover. This utility also could not test their ABB Advent Control System since ABB informed all their clients, with Advent, that following rollover to 2000, the system may irrevocably be damaged.

ú Utility WW runs a control algorithm on PCs, which accepted the 2000 rollover without any problems. The PCs were then cycled ON/OFF, whereupon the control systems locked-up due to error checking with the date stored in the real-time clock versus the DOS clock.

ú Utility XX tested the GE Mark V following a GE declaration that the Mark V is Y2K compliant. This utility uses the Mark V for several applications, including feedwater control. The Mark V locked-up following the roll-over to 2000 and locked in the last output signal to the feedwater regulating valves. (This would likely cause a plant shutdown)

ú Utility YY tested their energy management system (EMS) power calculation which failed during the rollover forcing the simulator to initiate a 25% down power.

ú Utility ZZ tested their DCS (Honeywell) at the component level with no notable problems. An integrated test was performed and the control function failed two weeks following the 2000 rollover due to a historian overload which was unable to write to disk on its weekly schedule.

ú Several utilities acknowledged that control devices lockup when configured with non-compliant configurators, either hand-held or PC based.


CONTINGENCY PLANS FOR YEAR 2000 NEW YEARS EVE


ú Ensure adequate staff is available to support plant problems and work arounds.

ú Setup alternative communications.

ú Use power plants in Australia and Europe as an early warning system.

ú Be ready for grid disturbances.
ú
Place older plants on spinning reserve.

Date stagger your equipment if possible to pace the operator work arounds.

Share Recommend | Keep | Reply | Mark as Last Read | Read Replies (2)

To: Judith Weintraub who wrote (19939)7/2/1998 4:55:00 PM
From: Mighty_Mezz   of 31646
 
Judith - #reply-5003149

Share Recommend | Keep | Reply | Mark as Last Read

To: Ken Salaets who wrote (19938)7/3/1998 3:15:00 AM
From: CYBERKEN   of 31646
 
Short interest about one day's average vol. That only shows that the shorts on this thread are a bunch of piss ants waiting to get crushed under a kid's tennis shoe.

Share Recommend | Keep | Reply | Mark as Last Read | Read Replies (1)

To: CalculatedRisk who wrote (19913)7/3/1998 3:17:00 AM
From: CYBERKEN   of 31646
 
Y2K minus 547 days.

Share Recommend | Keep | Reply | Mark as Last Read | Read Replies (1)

To: CYBERKEN who wrote (19942)7/3/1998 3:50:00 AM
From: Dale Baker   of 31646
 
If short interest is only 3 or 4% of the float, that means a short squeeze is virtually impossible. Nobody will be crushed by anything. Any positive news will draw in the daytraders again, who pump and dump.

You are trying to launch a 100-ton rocket which is getting heavier all the time through dilution, using a few gallons of regular gas.

Just my opinion.

Share Recommend | Keep | Reply | Mark as Last Read

To: paul boudreau who wrote (19940)7/3/1998 4:48:00 AM
From: Mark Jurik   of 31646
 
I'd like to provide a basis for an in-depth comparison on this and other Y2K firms, so I posted this message on many relevant boards. Please contribute. I'll collect useful comments from all boards, distill them and repost for all to benefit.

-------------------------------------------

Although we're all familiar with the profit potential in investing in this sector, where will investor's money flow? The perception of both the public and of fund managers are likely to be skewed in favor of different firms at different times. Although flow may be partially driven by expected EPS, likelihood of survival after Y2000, etc., the bottom line is which stock will appreciate quickly and reliably, and when.

While studying Y2K stocks for some time, I've noticed patterns forming. For example, there seems to be three groups of Y2K firms:

1) software vendors for do-it-yourself customers
2) consultants that will perform on/off site
3) automated factory conversion

The general mindset of corporate America is to try to solve the problem in-house. So group #1 gets the business first. If that fails, then the tendency is to hire consultants, and so group #2 gets the business. If that fails, then group #3 may get the business.

Given this scenario, which group is the best place to diversify within at this time? There are good arguments all around. For example, will the 70% that has yet to spend $$$ prefer to use group 1 tactics this late in the game? Rationally, they shouldn't, but waiting up to now to address the issue wasn't very smart to begin with. So rational thought is out the window.

Maybe the majority will prefer to hire consultants. The problem here is that there are very few consultants left to take on additional work. Wages will inevitably skyrocket and these Y2K firms can't simply pass on all the additional costs to the customer, else clients may be motivated to buy Y2K software and do it themselves. In this group, profit margins will likely dwindle.

Maybe the majority, seeing how little time is left will simply go for factory conversion. But where are the contracts? Is it mere coincidence that factory conversion companies have announced few, if any, new contracts this past quarter? Most firms in this class have had one or more losing quarters.

This has not gone unnoticed by investors. Now that the Y2K market correction has ended, I see money flow is beginning to return into the first two groups, but not the third. It may be because it's easier for institutional investors to justify buying stock in profitable companies than unprofitable ones at this time, despite the great future potential of factory conversion.

When discussing potential, I find it important to view not only the firm's true potential but the public's perception of that firm's potential as well. The public gets its information from investor forums, annual reports, trade shows, etc. The public is probably aware of the three classes of Y2K firms, but what about the different types of technology employed by the firms? For example, some firms only perform "forward" analysis, that is, they examine code, deduce where date related code exists and makes the needed modifications. Other firms also employ "reverse" analysis, where they examine databases produced by the code, detect date patterns embedded within, and infer where in the code these dates are being created. Is it worth it? Well, if reverse analysis can improve the "first time" success rate from 90 to 95%, that reduces the manually intensive part fixing-it-by-hand from 10% down to 5%, a 50% reduction in manual labor. A significant savings.

Another question regarding technology is whether or not the Y2K firm owns all the technology they employ. If not, can they get upgrades when needed? I've written reverse date analysis software for a Y2K firm, and it's likely some other firms have used outside contractors as well.

Joint ventures and teaming agreements also play a role in perceived future earnings. The more the merrier. Then again, maybe not. Although they feed the imagination with potential income, its still not income. One way to rate the quality of a teeming agreement is to see how long it has been since the agreement was announced and then ask how many contracts came from that agreement. Having many year+ teeming agreements but with only a few short-lived contracts says a lot. Is one teeming partner getting all the work, leaving the other with rare difficult-to-do "scraps"?

I'm sure there are lots of other issues as well. For example, a firm with good potential but no cash and losing quarters may be a likely buy-out prospect. How will shareholders be affected?

Another issue regarding rebounding stock action that I find useful is what I call "hidden resistance". Large shareholders of a stock who bought on the hope of making a nice profit have recently seen their equity dissipate during the recent Y2K correction that occurred the past 2 months. For some stocks it became obvious that no one was buying, especially when the sale of a mere 1000 shares would make the price fall 50 cents. So there's nothing to do but watch price fall, equity vaporize and frustration mount. After awhile, the investor may want to "get out" as soon as it appears he can break even; so he places a sell limit on a large order and this creates a "hidden resistance" against upward price action. I've seen it happen. Although the glass ceiling could be penetrated, the lack of momentum may encourage investors to place their bets on other Y2K firms, prolonging the stall on this stock even more.

In summary, the topics mentioned above are ...

1. The relative profitability and optimal timing of the three Y2K groups
2. Money flow into less risky, profitable firms
3. Forward and reverse analysis, public perception of its power
4. Who owns the technology?
5. Are teeming agreements producing contracts? Who's getting the work?
6. Buy-out prospects
7. Hidden resistance

Finally, word has it that Gingrich is forcing Clinton to speak up on Y2K in the next few weeks. This, in my opinion, will begin the major public move into the Y2K sector. Where will the $$$ go? That's what we can work together to find out.

I invite contributions from all who have something to say on any of the above, or other relevant topics not mentioned. Every bit helps and I will compile constructive comments from all the boards into a coherent reposting.

- Mark Jurik

Share Recommend | Keep | Reply | Mark as Last Read
Previous 10 | Next 10 

Copyright © 1995-2013 Knight Sac Media. All rights reserved.