Silicon Investor (SI) -- The First Internet Community

STOCKTALK

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.

Technology Stocks : Discuss Year 2000 Issues -- Ignore unavailable to you. Want to Upgrade?

To: John Mansfield who wrote (2183)	7/18/1998 5:18:00 PM
From: John Mansfield	Read Replies (1) \| Respond to of 9818

'Senator Bennett's speech has already been taken off the National Press Club's website. It is not on his Senate website either. > >WHY? Gee, he must have said something embarrassing for which a few muscles had to be flexed. This happens _ALL OF THE TIME_ in the world of Y2K! Not unlike the countless "Compliance Statements" that have been weakened or magically vaporized over the past six months for any of a host of reasons. One of the most recent hijackings brought to my attention was the spontaneous "disappearance" of not one, but TWO "compliance statements" from manufacturers of vital medical devices. It seems that there were these vicious rumors ... Perhaps NOW you may understand my extreme frustration with those who are so easily deceived by the lack of information or the mountains of deliberate disinformation through which we must sift. Spare me the platitudes, Pollyannas. Ciao, Scott Secor ___ 'Subject: Re: Sen. Bennett' speech removed!!!! Date: Fri, 17 Jul 1998 12:03:28 -0500 From: "D. Scott Secor - Millennial Infarction Mitigator" <y2k@uswest.net.NO$PAM> Organization: Bon Bahn Communications, Mpls., MN, USA Newsgroups: comp.software.year-2000 References: 1

To: John Mansfield who wrote (2183)	7/18/1998 5:40:00 PM
From: John Mansfield	Respond to of 9818

'Subject: Business Contingency Planning Date: 17 Jul 1998 04:28:35 GMT From: fix2000bug@aol.com (FIX2000BUG) Organization: AOL aol.com Newsgroups: comp.software.year-2000 I received an email from someone in this group who graciously thanked me for my "non-technical" contributions, and lamented that I wasn't involved "in the trenches" in some way to help in the the bug wars. He was mistaken. Please forgive me, fellow posters, for not formally introducing myself upon entrance into this most honorable gathering! Presently, I am involved in "Year 2000 Public Relations" and copywriting, helping companies explain the Y2k challenge to management, non-technical employees, and the Public. This includes but is not limited to corporate brochures, website copy, newsletters, vendor statements, and speech writing. Recently, Dr Leon Kappelman asked me to perform original Y2k "parodies" for SIM's SPG Year 2000 Conference in Chicago before each of the keynote speakers (Ed Yourdon, Capers Jones and Karl Feilder) gave their presentations, and to be the master of ceremonies for "Technology Theatre" in the exposition hall. Lately most of my time has been spent working on Contingency Planning. If you folks are like most of the project managers I have spoken with, you are beginning to discover that Y2k Contingency Planning goes beyond the traditional specifics of planning for contingencies related to one system: it is a broader effort that looks at potential failures in infrastructure, interfaces, data exchanges, supply chains, and the impact such failures may have on business operations. Y2k Contingency Planning now seems to be an obviously critical area of concern. The problem is that IT professionals have their hands full with repair efforts. Although it may change soon, most organizations are are still seeing this as an IT problem. As time runs out for IT repair jobs, it becomes more critical and timely to assess the potential Y2k impacts and to prepare plans for coping with them. Thus far, my contribution in the area of contingency planning has been to help stimulate the "right brain" activity necessary for a business to achieve their primary objective: maximize the speed and functionality of business resumption. This is accomplished in the following ways: Assistance in the description of the resources, staff roles, procedures, and timetables needed for Contingency Plan implementation. Assessment of costs and benefits of identified alternatives and selection of the best contingency strategies for each core business process. Identification and documentation of contingency plans and implementation modes. Definition and documentation of triggers for activating contingency plans. Establishment of a business resumption team for each core business process. Development and documentation of "zero-day" strategy and procedures. I am working to bring together a team of associates in order expand the range of our services to include the financial arena, the legal aspect (due diligence!) and vendor/supplier relations. Meanwhile, however, it is possible that I could help your company with the "broader picture" as you pursue a strategy that secures the best of both worlds: efficiency in remediation and repair, and preparedness for potential oversights. It has been said before: This is not a technical issue - - it is a management issue. Well, this is also a communication issue. This newsgroup is certainly a good place for sharpening communications skills! Feel free to email me privately for more information. :) Duane Schwingel Y2k Public Relations

To: John Mansfield who wrote (2183)	7/19/1998 5:22:00 AM
From: John Mansfield	Read Replies (2) \| Respond to of 9818

'Subject: Re: YOU SUNK MY BATTLESHIP! (Navy Software Dead in the Water) Date: 19 Jul 1998 00:07:18 GMT From: nospam@wwa.com (Bloody Viking) Organization: ACME Eternal Batteries, Ltd. Oslo, Minnesota. Newsgroups: comp.software.year-2000 References: 1 Theo DP (theodp@aol.com) wrote: : Navy Software Dead in the Water...Last week the US Navy acknowledged that the : USS Hue City and the USS Vicksburg -- two of the Navy's prize battle cruisers : -- will be out of commission until further notice as engineers try to integrate : new weapons control systems on the ships...The heart of the problem lies with : two new systems being built into the ships. The Aegis Baseline 6 system helps : defend the vessels against air attacks, and the Cooperative Engagement : Capability (CEC) system gathers and shares radar data from multiple ships. The Navy has lots of old weapon systems. The powerplants on older steam-driven ships will run though, as that equipment is REALLY backward. I mean, pneumatic-driven boiler controls where the "transistors" are pneumatic-driven valves - literally. The problem will be late-model ships like the gas turbine driven ones, and of course all the weapon systems, which frequently have discrete logic gates. Some fun stuff to watch for: The CIWS system, which is closely tied into the ship radars. (The CIWS is that R2D2 gatling gun device.) Also, antiaircraft missiles, and any nuclear tactical missile. The antiaircraft missiles are also tied into the radars, like the CIWS gatling guns. These systems can be configured in several ways, if one radar is busted. But if all the radars are busted, it's useless. Even funnier will be the CIC where all the information is fed into. It has largely taken over the function of the Bridge. (cab) It looks like a wierd video arcade in CIC. The Navy might consider dusting off the really old ships, with weapon systems that pre-date the computers, like the Iowa models.