FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W232086266> ?p ?o ?g. }

• W232086266 startingPage "6" @default.
• W232086266 abstract "The Year 2000 problem, or Y2K in popular speak, has been called everything from millennium bug to much ado about nothing. The scores of studies and hundreds of media reports to scope problem, its associated costs, and possible implications have produced a wide variety of conclusions, ranging from the end of world as we know to a bump in information superhighway. That there will be a global disruption is a given; extent and magnitude of crisis, on other hand, still remain to be determined. Over past six months, estimates of global cost for correcting Y2K problem have risen from $719 billion to $858 billion, an increase of 20 percent.(1) This makes Y2K second most expensive endeavor world has faced since World War II, whose total cost was approximately $4.2 trillion. Even Vietnam War--estimated at $500 billion--cost less. Who will be hurt, how badly, and for how long are all questions that are impossible to answer. While there is no way to predict which nations will be most at risk, United States is clearly ahead of pack in its compliance efforts, followed by Canada, Australia, South Africa, and Israel. The United Kingdom has slipped from second to sixth place but is still well ahead of Germany, France, Italy, and Japan. Unlike earthquakes or floods, which occur with little to no warning, we know when Y2K crisis will hit, which makes this disaster unique. now have just a few months to fix problem, test repairs, and develop adequate contingency plans to mitigate possible failures. Few people still believe we have time to fix all our critical Testifying before Senate Special Committee on Year 2000 Technology Problem, James Woodward of Cap Gemini, Europe's biggest software and services company, claimed that 83 percent of American companies expressed confidence in their mission-critical systems. (2) One of reasons for their lack of confidence is interconnectedness of problem; it is nor a question of one thing going wrong, but possibility of tens of thousands of little failures occurring all over world. As Bruce Webster, chairman of WDCY2K-- a group of more than 2,000 Y2K experts from greater Washington area--points out, We live in a network of multiple, complex, interacting systems and it's hard to tell where one system ends and another begins. When things fail, we will be facing multiple overlapping failures, not isolated events. General Motors, for instance, has over 100,000 suppliers and vendors. If even one of these data exchange partners is not fully compliant, whole system may become infected by corrupted data, which could result in significant errors or system crashes. Simple Mistake The Y2K crisis originated in a simple programming habit. Decades ago, memory space was very expensive--computer memory that might cost $5 today cost $5 million 30 years ago. As a result, most programmers allocated only two spaces to denote date field. At turn of century when last two digits roll back to 00, computers may mistakenly assume that date is 1900, not 2000. Even though most programmers knew, even 30 years ago, that this would cause problems come January 1, 2000, most did not believe that systems they were programming would still be in use. Dates are very important in computers since they are used extensively to make all kinds of calculations. For example, dates are used to determine who should receive Social Security checks, pensions, Medicare, retirement benefits, driver's licenses renewal, and tax refunds. In industry, dates control everything from manufacturing processes and just-in-time delivery systems, to maintenance schedules and assembly lines. The financial industry is most vulnerable, since it uses dates to control everything from trading to mortgage payments and credit card bills. No Quick Fix Even though solution to Y2K seems technically simple--expanding date field from two to four digits--the magnitude and complexity of problem is daunting. …" @default.
• W232086266 created "2016-06-24" @default.
• W232086266 creator A5018045629 @default.
• W232086266 creator A5039048616 @default.
• W232086266 date "1999-06-22" @default.
• W232086266 modified "2023-09-24" @default.
• W232086266 title "Technology Bites Back: The Millennium Bug Promises to Take Its Toll on Technology Systems around the Globe" @default.
• W232086266 hasPublicationYear "1999" @default.
• W232086266 type Work @default.
• W232086266 sameAs 232086266 @default.
• W232086266 citedByCount "0" @default.
• W232086266 crossrefType "journal-article" @default.
• W232086266 hasAuthorship W232086266A5018045629 @default.
• W232086266 hasAuthorship W232086266A5039048616 @default.
• W232086266 hasConcept C118487528 @default.
• W232086266 hasConcept C127413603 @default.
• W232086266 hasConcept C14331377 @default.
• W232086266 hasConcept C144133560 @default.
• W232086266 hasConcept C162324750 @default.
• W232086266 hasConcept C17744445 @default.
• W232086266 hasConcept C203014093 @default.
• W232086266 hasConcept C2775899829 @default.
• W232086266 hasConcept C2778025104 @default.
• W232086266 hasConcept C38652104 @default.
• W232086266 hasConcept C41008148 @default.
• W232086266 hasConcept C47768531 @default.
• W232086266 hasConcept C71924100 @default.
• W232086266 hasConceptScore W232086266C118487528 @default.
• W232086266 hasConceptScore W232086266C127413603 @default.
• W232086266 hasConceptScore W232086266C14331377 @default.
• W232086266 hasConceptScore W232086266C144133560 @default.
• W232086266 hasConceptScore W232086266C162324750 @default.
• W232086266 hasConceptScore W232086266C17744445 @default.
• W232086266 hasConceptScore W232086266C203014093 @default.
• W232086266 hasConceptScore W232086266C2775899829 @default.
• W232086266 hasConceptScore W232086266C2778025104 @default.
• W232086266 hasConceptScore W232086266C38652104 @default.
• W232086266 hasConceptScore W232086266C41008148 @default.
• W232086266 hasConceptScore W232086266C47768531 @default.
• W232086266 hasConceptScore W232086266C71924100 @default.
• W232086266 hasIssue "2" @default.
• W232086266 hasLocation W2320862661 @default.
• W232086266 hasOpenAccess W232086266 @default.
• W232086266 hasPrimaryLocation W2320862661 @default.
• W232086266 hasRelatedWork W1485868143 @default.
• W232086266 hasRelatedWork W155467968 @default.
• W232086266 hasRelatedWork W1554975518 @default.
• W232086266 hasRelatedWork W177856771 @default.
• W232086266 hasRelatedWork W1967478767 @default.
• W232086266 hasRelatedWork W2009528775 @default.
• W232086266 hasRelatedWork W2118162430 @default.
• W232086266 hasRelatedWork W215672444 @default.
• W232086266 hasRelatedWork W220340095 @default.
• W232086266 hasRelatedWork W2342699229 @default.
• W232086266 hasRelatedWork W287471064 @default.
• W232086266 hasRelatedWork W302045797 @default.
• W232086266 hasRelatedWork W311695254 @default.
• W232086266 hasRelatedWork W341441261 @default.
• W232086266 hasRelatedWork W341901058 @default.
• W232086266 hasRelatedWork W342337754 @default.
• W232086266 hasRelatedWork W348832691 @default.
• W232086266 hasRelatedWork W52668231 @default.
• W232086266 hasRelatedWork W63621401 @default.
• W232086266 hasRelatedWork W336885155 @default.
• W232086266 hasVolume "14" @default.
• W232086266 isParatext "false" @default.
• W232086266 isRetracted "false" @default.
• W232086266 magId "232086266" @default.
• W232086266 workType "article" @default.