DOCSLIB.ORG

Failure References.Pdf

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Failure References.Pdf Preventing slips, overruns, and cancellations: Application of accident investigations and theory to the understanding and prevention of engineering project failures D. C. Aloisio and K. Marais Department of Aeronautics and Astronautics, Purdue University, West Lafayette, IN, 47907 Supporting Data: Project Failure and Accident Reports used in Data Analysis Action, James M., & Hibbs, Mark. (2012). Why Fukushima Was Preventable. Washington, D.C.: Carnegie Endowment For International Peace. Alonso-Zaldivar, R. (2014, July 31). Probe Finds Reasons for Obamacare Website Failure. Retrieved from Inc: www.inc.com/associated-press/management-failure-results-in-healthcare.gov-woes.html ASC. (2002). In-Flight Breakup Over the Taiwan Strait China Airlines flight CI611. Aviation Safety Council. ASCE. (2007). The New Orleans Hurricane Protection System: What Went Wrong and Why. Reston: American Society of Civil Engineers Hurricane Katrina External Review Panel. Baker, J. (2007, January). The Report of The BP U.S. Refineries Independent Safety Review Panel. Texas City: BP. Bergin, C. (2006, January 4). X-33/VentureStar - What really happened. Retrieved from NASASpaceflight.com: www.nasaspaceflight.com/2006/01/x-33venturestar-what-really- happened/ Bradsher, K. (2000, December 7). Study of Ford Explorer's Design Reveals a Series of Compromises. The New York Times. Bylin, K. (2011, March 16). 4 Likely Causes of Micosoft Zune Death. Retrieved from hypebot: www.hypebot.com/hypebot/2011/03/4-likely-causes-of-the-death-of-the-zune.html Chandrasekaran, R. (2013, March 9). F-35's ability to evade budget cuts illustrates challenge of paring defense spending. The Washington Post. Ciralsky, A. (2013, September 16). Will It Fly? Retrieved from Vanity Fair: www.vanityfair.com/politics/2013/09/joint-strike-fighter-lockheed-martin Claybrook, J. (2000, September 12). Statement of Joan Claybrook On Firestone Tire Defect and Ford Explorer Rollovers. Retrieved from Public Citizen Auto Safety: www.citizen.org/autosafety/article_redirect.cfm?ID=5414 1 Cooke, D. L. (2003). A system dynamics analysis of the Westray mine disaster. System Dynamics Review, 19(2), 139-166. Coolman, A. (2014, October 30). Lessons Learned from Project Failure at Denver International Airport: Why Checking Bags is Still a Pain. Retrieved from Wrike: https://www.wrike.com/blog/lessons- learned-from-project-failure-at-denver-international-airport-why-checking-bags-is-still-a-pain/ Cowing, K. (2000, August 29). Iridium: If You Build It They Won't Necessarily Come. Retrieved from spaceref: www.spaceref.com/news/viewnews.html?id=208 CSB. (2007). Refinery Explosion and Fire. Washington, D.C.: United States Chemical Safety and Hazard Investigation Board. CSB. (2007). Xcel Energy Hydroelectric Plant Penstock Fire. Washington, D.C.: United States Chemical Safety and Hazard Investigation Board. CSB. (2008). Sugar Dust Explosion and Fire. Washington, D.C.: United States Chemical Safety and Hazard Investigation Board. CSB. (2010). Final Report: Kleen Energy Urgent Recommendations. Washington, D.C.: United States Chemical Safety and Hazard Investigation Board. CSB. (2014). Explosion and Fire at the Macondo Well. Washington, D.C.: United Staes Chemical Safety and Hazard Investigation Board. CTI. (2013). Hearing on "How to Improve the Efificiency, Safety and Security of Maritime Transportation: Better use and Integration of Maritime Domain Awareness Data.". Washington, D.C.: United States Committee on Transportation and Infrastructure. CTSA. (1997). Inquiry into the fire on Heavy goods Vehicle shuttle 7539 on 18 November 1996. The Channel Tunnel Safety Authority. Cullen, W. (1990). The Public Inquiry into the Piper Alpha Disaster. London: United Kingdom Department of Energy. Dawes, Sharon S., & Nelson, Mark R. (1995). Pool the Risks, Share the Benefits: Partnerships in IT Innovation. In J. Keyes, Technology Trendlines: Technology Success Stories from Today's Visionaries (pp. 125-131). Hoboken: Wiley. de Neufville, R. (1994). The Baggage System at Denver: Prospects and Lessons. Journal of Air Transport Management, 1(4), 229-236. Denning, S. (2013, January 21). What Went Wrong At Boeing? Retrieved from Forbes: www.forbes.com/sites/stevedenning/2013/01/21/what-went-wrong-at-boeing/print/ Dilger, D. E. (2008, February 21). Lessons from the Death of HD-DVD. Retrieved from RoughlyDrafted: www.roughlydrafted.com/2008/02/21/lessons-from-the-death-of-hd-dvd/ DOT. (2014). Management Advisory on Weaknesses With Site-Specific Deployment Requirements and Specialist Training for STARS. Washington, D.C.: United States Department of Transportation. 2 Dvorak, J. C. (2008, April 21). Vista's 11 Pillars of Failure. Retrieved from PCMag: www.pcmag.com/article2/0,2817,2286065,00.asp Eckerman, I. (2005). The Bhopal Saga--Causes and Consequences of the World's Largest Industrial Disaster. Bhopal: Universities Press (India). Enderle, R. (2011, March 15). RIP Zune: How Microsoft could have succeeded. Retrieved from TG Daily: www.tgdaily.com/opinion/54687-rip-zune-how-microsoft-could-have-succeeded ESA & NASA. (1998). SOHO Mission Interruption. Greenbelt: Joint ESA/NASA Investigation Board. Finkelsten, S., & Sandord, S. (2000). Learning from Corporate Mistakes: The Rise and Fall of Iridium. Organizational Dynamics, 29(2), 138-148. Gallagher, S. (2014, March 28). Littoral failure: Navy hedges bets on high-tech littoral combat ships. Retrieved from Ars Technica: arstechnica.com/tech-policy/2014/03/littoral-failure-navy-hedges- bets-on-high-tech-littoral-combats/ GAO. (1993). Problems Continue to Plague the Seawolf Submarine Program. Washington, D.C.: United States General Accounting Office. GAO. (1994). Navy Ships: Lessons or Prior Programs May Reduce New Attack Submarine cost Increases and Delays. Washington, D.C.: United States General Accounting Office. Gehman, H. (2003). Columbia Accident Investigation Board Report. Washington, D.C.: Columbia Accident Investigation Board. Gelbart, M. (2003, June 10). New radar system cleared to take off STARS, which was being tested by air traffic controllers in Philadelphia, won U.S. approval. The cost: $1 billion-plus. Retrieved from philly: articles.philly.com/2003-06-10/business/25447572_1_radar-system-terminal- automation-replacement-system-air-traffic-control-system Gelinas, N. (2007, Autumn). Lessons of Boston's Big Dig. Retrieved from City Journal: www.city- journal.org/html/17_4_big_dig.html Gertler, J. (2009). V-22 Osprey Tilt-Rotor Aircraft: Background and Issues for Congress. Washington, D.C.: United States Congressional Research Service. Graham, B., & Reilly, W. (2011). Deep Water: The Gulf Oil Disaster and the Future of Offshore Drilling. National Commission on the BP Deepwater Horizon Oil Spill and Offshore Drilling. Hollmer, M. (2002). Segway poses challenge for pedestrians and insurers. Insurance Times, XXI(17). Honan, M. (2013, August 5). Remembering the Apple Newton's prophetic failure and lasting impact. Retrieved from Wired: www.wired.com/2013/08/remembering-the-apple-newtons-prophetic- failure-and-lasting-ideals/ Hormby, T. (2013, August 6). The Story Behind Apple's Newton. Retrieved from Low End Mac: lowendmac.com/2013/the-story-behind-apples-newton/ 3 Howell, K. (2014, August 18). FAA's new air traffic control system unstable, less capable than old system. Retrieved from Washington Times: www.washingtontimes.com/news/2014/aug/18/faas- terminals-system-upgrade-would-waste-438m-ig/?page=all IAEA. (1992). The Chernobyl Accident. Vienna: International Atomic Energy Agency. Ingram, C. (1994, April 27). DMV Spent $$ Million on Failed Project. Retrieved from LA Times: articles.latimes.com/1994-04-27/news/mn-50941_1_modernization-project Johnson, K. (2005, August 27). Denver Airport Saw the Future. It Didn't Work. Retrieved from The New York Times: http://www.nytimes.com/2005/08/27/us/denver-airport-saw-the-future-it-didnt- work.html JPL Special Review Board. (22 March 2000). Report on the Loss of the Mars Polar Lander and Deep Space 2 Missions. Pasadena: United States National Aeronautics and Space Administration Jet Propulsion Lab. Kaeding, N. (2015). The Failed HealthCare.gov Launch. Cato Institute. Kemeny, J. G. (1979). Report of The President's Commission On The Accident At Three Mile Island. Washington, D.C.: The President's Commission On The Accident At Three Mile Island. Khan, Faisal I., & Amyotte, Paul R. (2007). Modeling of BP Texas City refinery incident. Journal of Loss Prevention in the Process Industries, 20, 387-395. Kumar, A. (2001, June 17). Attention shifts from Firestone to Ford Explorer. Retrieved from St. Petersburg Times: www.sptimes.com/News/061701/news_pf/Firestone/Attention_shifts_from.shtml Kurokawa, K. (2012). The official report of The Fukushima Nuclear Accident Independent Investigation Commission. The National Diet of Japan Fukushima Nuclear Accident Independent Investigation Commission. Laing, R. D. (2002). Report of the Commission of Inquiry into matters relating to the safety of the public drinking water in the City of. Regina: The office of the Queen's Printer. Langewiesche, W. (1998, March). The Lessons of ValuJet 592. Retrieved from The Atlantic: https://www.theatlantic.com/magazine/archive/1998/03/the-lessons-of-valujet-592/306534/ Lipton, E. (2006, December 30). Security Effort by Coast Guard Is Falling Short. Retrieved from The New York Times: www.nytimes.com/2006/12/30/us/30domain.html?pagewanted=print MacDonald, G. (2011). Buncefield: Why did it happen? Competant Authority for the Control of Major Accident Hazards. Marks, G. (2014,
Load more

Recommended publications
  • Transcript of Rick Rashid's Keynote Address
    TechFest 2013 Keynote Rick Rashid March 5, 2013 ANNOUNCER: Ladies and gentlemen, please welcome Microsoft Chief Research Officer, Rick Rashid. (Applause.) RICK RASHID: Hi there. Well, hopefully this will be a very fun day for all of you. For me, it's interesting. It feels like we've been doing TechFest for a really, long time, but it's actually only been since 2001. So, technically, I think, this is the 13th TechFest event for Microsoft Research. Of course, in the first TechFest, it wasn't nearly as big an event as this. It was just for employees. We didn't take up nearly as much space. And we didn't even know how many people would really show up. I was actually one of the strongest skeptics about this whole idea of creating this technology show for our employees, because I wasn't really sure how many people would show up. I kept saying, “Well, gosh, it seems like it's going to be a lot of work, and I'm not sure it's going to be really valuable and worthwhile, but if you guys really think you want to do it, okay.” Of course, what happened that year was we had, I think, about 4,000 of our Puget Sound employees come over a two-day period. And of course Microsoft was a much smaller company back then, so that was just a huge fraction of our Puget Sound workforce at that time. And everybody was really excited. I mean, the researchers came away from the event really excited about being able to talk to so many of our employees, be able to interact with them, and to sort of sell their ideas, and show off what they've been doing.
    [Show full text]
  • Microsoft Plays Hardball: Use of Exclusionary Pricing and Technical
    Antitrust Bulletin, XL:2, Summer 1995, 265-315 MICROSOFT PLAYS HARDBALL: The Use of Exclusionary Pricing and Technical Incompatibility to Maintain Monopoly Power in Markets for Operating System Software† by KENNETH C. BASEMAN* FREDERICK R. WARREN-BOULTON* and GLENN A. WOROCH** May 1995 ___________________ * Principals, MiCRA: Microeconomic Consulting and Research Associates, Inc., Washington, DC. ** University of California, Berkeley. † Forthcoming, Antitrust Bulletin, June 1995. We would like to express our appreciation for helpful comments and other assistance to Sturge Sobin, Linnet Harlan, Paul Dennis and the participants at the Columbia Business School's Institute for Tele-Information's Seminar on Sustaining Competition in Network Industries through Regulating and Pricing Access, especially Janusz Ordover and Bobby Willig. TABLE OF CONTENTS I. INTRODUCTION AND SUMMARY ................................... 1 II. BACKGROUND .................................................... 3 A. THE MARKET FOR PERSONAL COMPUTER OPERATING SYSTEMS ............................................................ 3 TABLE: NEW SHIPMENTS OF PERSONAL COMPUTER OPERATING SYSTEMS .............................................. 8 B. MICROSOFT'S PRACTICES ..................................... 9 III. FIRST-DEGREE PRICE DISCRIMINATION vs. INEFFICIENT SUBSTITUTION ................................................... 15 A. FIRST-DEGREE PRICE DISCRIMINATION ........................ 16 B. INEFFICIENT SUBSTITUTION ................................. 20 IV. ANTIFRAUD AND ANTIPIRACY
    [Show full text]
  • UI Design and Interaction Guide for Windows Phone 7
    UI Design and Interaction Guide 7 for Windows Phone 7 July 2010 Version 2.0 UI Design and Interaction Guide for Windows Phone 7 July 2010 Version 2.0 This is pre-release documentation and is subject to change in future releases. This document supports a preliminary release of a software product that may be changed substantially prior to final commercial release. This docu- ment is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document. Information in this document, including URL and other Internet Web site references, is subject to change without notice. The entire risk of the use or the results from the use of this document remains with the user. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this docu- ment. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
    [Show full text]
  • Use Your PC for Music
    WINDOWS® GUIDE Use Your PC for Music IN THIS GUIDE Rip and Burn CDs Page 2 Play Music Page 10 Connect an MP3 Player Page 14 Use a Music Service Page 17 What You’ll Need n Windows Media® Player—available as a free download n Recordable or rewritable audio or data CDs n A CD Burner n A Windows Media-enabled media device, such as a Windows Mobile® device or Zune® n A computer running Windows Vista® Windows Guides is a library of easy-to-use guides that show you how to get more from your Windows experience. Share these guides with your friends and family. © 2008 Microsoft. All rights reserved. WINDOWS GUIDE Use Your PC for Music Rip and Burn CDs Nowadays, most of us don’t just own a handful of albums. Music is a way of life. We want to be able to buy, organize and play songs on a whim, and take them with us wherever we go. Well, Windows Media Player takes the work out of building and maintaining a music library, so your only worry is what to listen to first. RIP A CD Ripping, or encoding, your impressive CD library into a digital one with Windows Media Player is quick and simple. There are two things to consider before ripping a CD: n By default, ripped songs are stored as Windows Media Audio (WMA) files. WMA is the best format to use for playing on Windows Media Player, but if for some reason you’d like to choose a different format: 1.
    [Show full text]
  • Why I Hate Microsoft by F.W
    Why I hate Microsoft by F.W. van Wensveen Why I hate Microsoft "A personal, lengthy, but highly articulate outburst" by F.W. van Wensveen Table of contents Introduction A brief introduction, or why this paper needed to be written Abstract The management summary 1. From the people who brought you EDLIN Microsoft and innovation 2. The not-so-good, the bad and the ugly The general quality of Microsoft products 3. The power to bind Formats and standards 4. World domination From business to megalomania 5. Bad practice, foul play Exploring the limits of lawful conduct 6. Caveat Emptor Think before you buy 7. Where are you forced to go today? Price gouging and other monopolist practices 8. The road ahead On diminishing returns and continuing trends Appendix A A brief overview of Windows' most serious design flaws Appendix B Links Introduction "One OS to bring them all and in the darkness bind them..." From the title of this paper you may have guessed that I am not very impressed with the guys in Redmond. One might even say that my dislike for Microsoft is a pet hate gone out of control in an almost quixotic fashion. Why is this? Of course I have been accused of personal antipathy, of being jealous of Bill Gates and his billions, and of being prejudiced against all things Microsoft without any reason whatsoever. None of this is true. I have nothing personal against Bill Gates. Why should I? I don't know the man, I've never met him. I agree with those who say he might be the most successful salesman in history.
    [Show full text]
  • 3.3. Cloud Computing
    國 立 交 通 大 學 企業管理碩士學位學程 碩 士 論 文 網路泡沫化危機的十年之後: 谷歌個案研究 10 years after the dot-com bubble: A Case Study of Google 研 究 生：張倍菁 指導教授：劉芬美 中華民國一百零一年一月 10 years after the dot-com bubble: A Case Study of Google 研 究 生：張倍菁 Student: Penny Pei-ching Chang 指導教授：劉芬美 Advisor: Dr. Fen-May Liou 國 立 交 通 大 學 管理學院 企業管理碩士學位學程 碩 士 論 文 A Thesis Submitted to Master Degree Program of Global Business Administration College of Management National Chiao Tung University In partial Fulfillment of the Requirements For the Degree of Master in Business Administration January 2012 Hsinchu, Taiwan, Republic of China 中華民國一百零一年一月 National Chiao Tung University College of Management Global Master of Business Administration Program Thesis 網路泡沫化危機的十年之後: 谷歌個案研究 10 years after the dot-com bubble: A Case Study of Google Student: Penny Pei-ching Chang Advisor: Dr. Fen-May Liou Abstract Google is a legendary company famous with its rapid growth no matter being through dot-com bubble or even in the latest global financial crisis in 2008. Google started from web search engine then online keyword advertising. Recently it even moves its step into mobile and cloud computing areas. In this research, there are not only a wide vision of Google’s key success factors being discussed but a comprehensive corporate comparison among Google main competitors Yahoo! and Microsoft. This research first gives a fundamental analysis among these three companies by comparing their products development and key milestone. Then look into the business model they have been deployed. Although it seems to have the similarity among these three internet giants, this research points out the distinction between Google and other competitors.
    [Show full text]
  • Taking the Metro with Windows Phone
    1 Taking the Metro with Windows Phone WHAT ’ S IN THIS CHAPTER ➤ How Windows Phone has changed Microsoft ’ s approach to the mobile industry ➤ What the Metro Design Language is and how it came about ➤ An overview of the Start and Lock Screens and how they help users access information on the phone ➤ Why the use of Hubs creates a more connected user experience ➤ What it means to be a Windows Phone developer Microsoft has been building mobile devices for well over 10 years, starting with a variety of Windows CE- based devices, such as the Handheld PC and the Palm- size PC, fi rst released in 1996. Beginning around 2000, these disparate operating systems began converging into what became Windows Mobile, based on the principle of delivering a PC to your pocket. New features were predominately driven by enterprise needs such as device management and security. This eventuallyCOPYRIGHTED worked to the detriment ofMATERIAL the platform as it didn’ t appeal to the average consumer. Devices were more robust than sexy, and the user interface mirrored that of the desktop, even having a Start menu, rather than providing an experience. Throughout this chapter, and in other parts of this book, there will be references to both Windows Mobile and Windows Phone . This is intentional, and they are not the same thing. Windows Mobile refers to the previous mobile operating system from Microsoft that at the time of writing is Windows Mobile 6.5.3. Windows Phone refers to Microsoft ’ s latest offering in the mobile space and starts with Windows Phone 7.
    [Show full text]
  • Using History to Teach Computer Science and Related Disciplines
    Computing Research Association Using History T o T eachComputer Science and Related Disciplines Using History To Teach Computer Science and Related Disciplines Edited by Atsushi Akera 1100 17th Street, NW, Suite 507 Rensselaer Polytechnic Institute Washington, DC 20036-4632 E-mail: [email protected] William Aspray Tel: 202-234-2111 Indiana University—Bloomington Fax: 202-667-1066 URL: http://www.cra.org The workshops and this report were made possible by the generous support of the Computer and Information Science and Engineering Directorate of the National Science Foundation (Award DUE- 0111938, Principal Investigator William Aspray). Requests for copies can be made by e-mailing [email protected]. Copyright 2004 by the Computing Research Association. Permission is granted to reproduce the con- tents, provided that such reproduction is not for profit and credit is given to the source. Table of Contents I. Introduction ………………………………………………………………………………. 1 1. Using History to Teach Computer Science and Related Disciplines ............................ 1 William Aspray and Atsushi Akera 2. The History of Computing: An Introduction for the Computer Scientist ……………….. 5 Thomas Haigh II. Curricular Issues and Strategies …………………………………………………… 27 3. The Challenge of Introducing History into a Computer Science Curriculum ………... 27 Paul E. Ceruzzi 4. History in the Computer Science Curriculum …………………………………………… 33 J.A.N. Lee 5. Using History in a Social Informatics Curriculum ....................................................... 39 William Aspray 6. Introducing Humanistic Content to Information Technology Students ……………….. 61 Atsushi Akera and Kim Fortun 7. The Synergy between Mathematical History and Education …………………………. 85 Thomas Drucker 8. Computing for the Humanities and Social Sciences …………………………………... 89 Nathan L. Ensmenger III. Specific Courses and Syllabi ………………………………………....................... 95 Course Descriptions & Syllabi 9.
    [Show full text]
  • Why Software Firms Build Hardware – and What Microsoft Is Doing About It
    Why Software Firms Build Hardware – And What Microsoft Is Doing About It by Ryan M. Shaffer B.S. Electrical Engineering Grove City College, 2008 M.S. Computer Science Boston University, 2011 SUBMITTED TO THE SYSTEM DESIGN AND MANAGEMENT PROGRAM IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF MASTER OF SCIENCE IN ENGINEERING AND MANAGEMENT AT THE MASSACHUSETTS INSTITUTE OF TECHNOLOGY FEBRUARY 2015 © Ryan M. Shaffer. All rights reserved. The author hereby grants to MIT permission to reproduce and to distribute publicly paper and electronic copies of this thesis document in whole or in part in any medium now known or hereafter created. Signature of Author: _____________________________________________________ System Design and Management Program January 9, 2015 Certified by: ____________________________________________________________ Michael Cusumano Sloan Management Review Professor in Management Thesis Supervisor Accepted by: ___________________________________________________________ Patrick Hale Director, System Design and Management Fellows Program Why Software Firms Build Hardware – And What Microsoft Is Doing About It by Ryan M. Shaffer Submitted to the System Design and Management Program on January 9, 2015 in Partial Fulfillment of the Requirements for the Degree of Master of Science in Engineering and Management ABSTRACT Many software companies build first-party hardware products due to the trend toward smaller, more highly-integrated devices, along with the fast pace of innovation in the technology industry. Building hardware products does not always lead to success and actually creates a financial risk for the company by significantly reducing profit margins as compared to the traditional profit margins to which large software companies are accustomed. Three specific strategies are observed which firms have used successfully in this area.
    [Show full text]
  • Microsoft—Kinect for Windows
    Microsoft—Xbox Live, Games for Windows Live, Zune, and Windows Phone Marketplace Consumer Demand for Arbitration before the American Arbitration Association AMERICAN ARBITRATION ASSOCIATION SUPPLEMENTARY PROCEDURES FOR CONSUMER-RELATED DISPUTES Instructions for filing an arbitration claim: 1. Please fill out this form and keep a copy for your records. 2. Mail two (2) copies of this form and your check or money order to the nearest American Arbitration Association Case Management Center. Please consult Section C-8 of the AAA Supplementary Procedures for Consumer-Related Disputes for the required fee. You can find the AAA rules, the nearest Case Management Center, and the fee at www.adr.org or by calling the AAA at (800) 778-7879. Please make your check or money order payable to the American Arbitration Association. 3. Mail a copy of this form and a copy of your check or money order to Microsoft Corporation, LCA Arbitration, One Microsoft Way, Redmond, WA 98052-6399. Upon receipt, Microsoft will reimburse you for your filing fee if your claim is for $75,000 or less. 4. Please include the attached copies of the Terms of Use for Xbox Live, Games for Windows Live, Zune, and Windows Phone Marketplace with each copy of this form you mail. Your Information: Name: Address: City/State/Zip: Phone: Fax: E-mail address: Gamertag Zune tag (if Zune at issue) Windows Live ID Disputes involving $10,000 or less are usually resolved by the submission of documents. If a hearing is held, it will usually be telephonic. In disputes involving more than $10,000, a telephonic or in-person hearing will be held.
    [Show full text]
  • Microsoft—Kinect for Windows
    Microsoft Software, Devices, and Services with Arbitration Agreements Consumer Demand for Arbitration before the American Arbitration Association Instructions for filing an arbitration claim with American Arbitration Association: 1. Please fill out this form and keep a copy for your records. 2. Mail a copy of this form and your check or money order for $200 to American Arbitration Association, Case Filing Services, 1101 Laurel Oak Road, Suite 100, Voorhees, NJ 08043. Make your check or money order payable to American Arbitration Association. Please consult the AAA Consumer Arbitration Rules for more information. You can find them at www.adr.org or by calling the AAA at (800) 778-7879. 3. Please copy (or download and print) and mail to AAA (with this form and your check) your agreement with an arbitration clause (for example, Microsoft Services Agreement, Xbox Live Terms of Use, Xbox One Limited Warranty, Microsoft Software License Agreement Windows 8, Nokia Limited Warranty, etc.). If you don’t have your agreement, you can find most at www.microsoft.com/about/legal/en/us/arbitration/default.aspx 4. Mail a copy of this form, a copy of your Microsoft agreement, and a copy of your check or money order to Microsoft Corporation, LCA Arbitration, One Microsoft Way, Redmond, WA 98052-6399. Upon receipt, Microsoft will reimburse you for your $200 filing fee if your claim is for $75,000 or less. Your Information: Name: Address: City/State/Zip: Phone: Fax: E-mail address: Gamertag (for Xbox) Zune tag (for Zune) Microsoft account (was Windows Live ID) Disputes involving $25,000 or less are usually resolved by the submission of documents.
    [Show full text]
  • Downloaded in Jan 2004; "How Smartphones Work" Symbian Press and Wiley (2006); "Digerati Gliterati" John Wiley and Sons (2001)
    HOW OPEN SHOULD AN OPEN SYSTEM BE? Essays on Mobile Computing by Kevin J. Boudreau B.A.Sc., University of Waterloo M.A. Economics, University of Toronto Submitted to the Sloan School of Management in partial fulfillment of the requirements for the degree of MASSACHUBMMIBE OF TECHNOLOGY Doctor of Philosophy at the AUG 2 5 2006 MASSACHUSETTS INSTITUTE OF TECHNOLOGY LIBRARIES June 2006 @ 2006 Massachusetts Institute of Technology. All Rights Reserved. The author hereby grn Institute of Technology permission to and to distribute olo whole or in part. 1 Signature ot Author.. Sloan School of Management 3 May 2006 Certified by. .............................. ............................................ Rebecca Henderson Eastman Kodak LFM Professor of Management Thesis Supervisor Certified by ............. ................ .V . .-.. ' . ................ .... ...... Michael Cusumano Sloan Management Review Professor of Management Thesis Supervisor Certified by ................ Marc Rysman Assistant Professor of Economics, Boston University Thesis Supervisor A ccepted by ........................................... •: °/ Birger Wernerfelt J. C. Penney Professor of Management Science and Chair of PhD Committee ARCHIVES HOW OPEN SHOULD AN OPEN SYSTEM BE? Essays on Mobile Computing by Kevin J. Boudreau Submitted to the Sloan School of Management on 3 May 2006, in partial fulfillment of the requirements for the degree of Doctor of Philosophy Abstract "Systems" goods-such as computers, telecom networks, and automobiles-are made up of mul- tiple components. This dissertation comprises three esssays that study the decisions of system innovators in mobile computing to "open" development of their systems to outside suppliers and the implications of doing so. The first essay considers this issue from the perspective of which components are retained under the control of the original innovator to act as a "platform" in the system.
    [Show full text]