Miami - Why is MRO software so complicated

3,325 views

Published on

Why is MRO Software so complicated? What does the future hold?
Here's my presentation I did at the Miami Aircraft Commerce Aviation IT Conference March 2011

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,325
On SlideShare
0
From Embeds
0
Number of Embeds
994
Actions
Shares
0
Downloads
74
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Miami - Why is MRO software so complicated

  1. 1. why is MRO software so complicated …and what does the future hold?
  2. 2. questions, comments & arguments @conduce paul.saunders@conduce.net
  3. 3. why isn’t MRO software simpler? questions @conduce paul.saunders@conduce.net
  4. 4. the concorde cockpit comments @conduce paul.saunders@conduce.net
  5. 5. the airbus 380 cockpit arguments @conduce paul.saunders@conduce.net
  6. 6. don’t agree? @conduce paul.saunders@conduce.net
  7. 7. debate? @conduce paul.saunders@conduce.net
  8. 8. what?? @conduce paul.saunders@conduce.net
  9. 9. wtf?? @conduce paul.saunders@conduce.net
  10. 10. when did you last hear this software isn’t complex enough questions @conduce paul.saunders@conduce.net
  11. 11. when did you last hear we should get the most complex software money can buy questions @conduce paul.saunders@conduce.net
  12. 12. when did you last hear we’re happy because our software is so complex questions @conduce paul.saunders@conduce.net
  13. 13. when did you last hear i just want to get aircraft out of the door questions @conduce paul.saunders@conduce.net
  14. 14. when did you last hear i just want to get aircraft out of the door questions @conduce paul.saunders@conduce.net
  15. 15. when did you last hear i just want to get aircraft out of the door questions @conduce paul.saunders@conduce.net
  16. 16. when did you last hear i just want to get aircraft out of the door questions @conduce paul.saunders@conduce.net
  17. 17. what do i mean by “simpler”? your 2 cents @conduce paul.saunders@conduce.net
  18. 18. what do i mean by “simpler”?its about providing theright tool for the job…. and nothing else your 2 cents @conduce paul.saunders@conduce.net
  19. 19. what do i mean by “simpler”?“perfection is achieved notwhen there is nothing more to add, but when there isnothing left to take away.“ Antoine de Sainte-Expury the author of “The Little Prince” your 2 cents @conduce paul.saunders@conduce.net
  20. 20. why MRO software isn’t simpler the excuses questions @conduce paul.saunders@conduce.net
  21. 21. why MRO software isn’t simpler …MRO processes are really complex questions @conduce paul.saunders@conduce.net
  22. 22. People who say “MRO processesare really complex” have never been: • Rocket scientists • Brain surgeons • Any other kind of surgeon • Infant school teachers • Enigma code crackers • Inventors of the internet • Astronauts • Mathematicians • Particle physicists • Inventors of automatic anti-sniper systems • Able to programme a VCR • Involved in Middle East peace talks • A UN weapons inspector • Google algorithm designers • Etc Etc… a very long list questions @conduce paul.saunders@conduce.net
  23. 23. People who say “MRO processesare really complex” have never been: • Rocket scientists • Brain surgeons • Any other kind of surgeons • Infant school teachers • Enigma code crackers • Inventors of the internet • Astronauts • Mathematicians • Particle physicists • Inventors of automatic anti-sniper systems • Able to programme a VCR • Involved in Middle East peace talks • A UN weapons inspector • Google algorithm designers • Etc Etc… a very long list questions @conduce paul.saunders@conduce.net
  24. 24. People who say “MRO processesare really complex” have never been: • Rocket scientists • Brain surgeons • Any other kind of surgeons • Infant school teachers • Enigma code crackers • Inventors of the internet • Astronauts • Mathematicians • Particle physicists • Inventors of automatic anti-sniper systems • Able to programme a VCR • Involved in Middle East peace talks • A UN weapons inspector • Google algorithm designers • Etc Etc… a very long list questions @conduce paul.saunders@conduce.net
  25. 25. People who say “MRO processesare really complex” have never been: • Rocket scientists • Brain surgeons • Any other kind of surgeons • Infant school teachers • Enigma code crackers • Inventors of the internet • Astronauts • Mathematicians • Particle physicists • Inventors of automatic anti-sniper systems • Able to programme a VCR • Involved in Middle East peace talks • A UN weapons inspector • Google algorithm designers • Etc Etc… a very long list questions @conduce paul.saunders@conduce.net
  26. 26. why MRO software isn’t simpler …the regulations won’t allow change questions @conduce paul.saunders@conduce.net
  27. 27. why MRO software isn’t simpler …the regulations won’t allow change where does it say that mro software must be really complex and cannot be made simpler?? questions @conduce paul.saunders@conduce.net
  28. 28. why MRO software isn’t simpler …the mro companies are to blame questions @conduce paul.saunders@conduce.net
  29. 29. why MRO software isn’t simpler …the mro companies are to blame …maybe they don’t know any better questions @conduce paul.saunders@conduce.net
  30. 30. the hard facts for mro companies paradigm shift #1 people starting work now don’t know a world without the internet questions @conduce paul.saunders@conduce.net
  31. 31. the hard facts for mro companies paradigm shift #2 technology is no longer a barrier questions @conduce paul.saunders@conduce.net
  32. 32. why MRO software isn’t simpler …the sales process is to blame questions @conduce paul.saunders@conduce.net
  33. 33. why MRO software isn’t simpler …the sales process is to blame …maybe they don’t know any better questions @conduce paul.saunders@conduce.net
  34. 34. why MRO software isn’t simpler …the software vendors are to blame questions @conduce paul.saunders@conduce.net
  35. 35. why MRO software isn’t simpler …the software vendors are to blame …maybe they don’t know any better questions @conduce paul.saunders@conduce.net
  36. 36. why MRO software isn’t simpler …the software vendors are to blame …maybe they don’t know any better ……“well they should!!” questions @conduce paul.saunders@conduce.net
  37. 37. why MRO software isn’t simpler …its too difficult to change questions @conduce paul.saunders@conduce.net
  38. 38. how to make MRO software simpler questions @conduce paul.saunders@conduce.net
  39. 39. how to make MRO software simpler its all about the user experience questions @conduce paul.saunders@conduce.net
  40. 40. how to make MRO software simpler questions @conduce paul.saunders@conduce.net
  41. 41. how to make MRO software simpler questions @conduce paul.saunders@conduce.net
  42. 42. how to make MRO software simpler You are not designing for you, but designing for your users questions @conduce paul.saunders@conduce.net
  43. 43. how to make MRO software simpler don’t design for experts questions @conduce paul.saunders@conduce.net
  44. 44. how to make MRO software simpler don’t design by committee questions @conduce paul.saunders@conduce.net
  45. 45. how to make MRO software simpler hide stuff questions @conduce paul.saunders@conduce.net
  46. 46. how to make MRO software simpler shrink stuff questions @conduce paul.saunders@conduce.net
  47. 47. how to make MRO software simpler get rid of stuff questions @conduce paul.saunders@conduce.net
  48. 48. MRO software in the future questions @conduce paul.saunders@conduce.net
  49. 49. MRO software in the future work vs play questions @conduce paul.saunders@conduce.net
  50. 50. MRO software in the future work vs play questions @conduce paul.saunders@conduce.net
  51. 51. MRO software in the future work vs play questions @conduce paul.saunders@conduce.net
  52. 52. MRO software in the future work vs play questions @conduce paul.saunders@conduce.net
  53. 53. MRO software in the future work vs play questions @conduce paul.saunders@conduce.net
  54. 54. MRO software in the future mobilisation not miniaturisation questions @conduce paul.saunders@conduce.net
  55. 55. MRO software in the future mobilisation not miniaturisation screen real estate questions @conduce paul.saunders@conduce.net
  56. 56. MRO software in the future mobilisation not miniaturisation screen real estate questions @conduce paul.saunders@conduce.net
  57. 57. MRO software in the future mobilisation not miniaturisation battery life questions @conduce paul.saunders@conduce.net
  58. 58. MRO software in the future mobilisation not miniaturisation network latency questions @conduce paul.saunders@conduce.net
  59. 59. MRO software in the future mobilisation not miniaturisation device specific context questions @conduce paul.saunders@conduce.net
  60. 60. MRO software in the future mobilisation not miniaturisation questions @conduce paul.saunders@conduce.net
  61. 61. MRO software in the future mobilisation not miniaturisation native apps vs web apps questions @conduce paul.saunders@conduce.net
  62. 62. MRO software in the future mobilisation not miniaturisation iOS vs Android 3 questions @conduce paul.saunders@conduce.net
  63. 63. MRO software in the future mobilisation not miniaturisation everything on tablets questions @conduce paul.saunders@conduce.net
  64. 64. MRO software in the future a shift towards openness questions @conduce paul.saunders@conduce.net
  65. 65. MRO software in the future a shift towards openness 1. open data questions @conduce paul.saunders@conduce.net
  66. 66. MRO software in the future a shift towards openness 1. open data 2. open architecture questions @conduce paul.saunders@conduce.net
  67. 67. MRO software in the future a shift towards openness 1. open data 2. open architecture 3. open source questions @conduce paul.saunders@conduce.net
  68. 68. MRO software in the future a shift towards openness 1. open data 2. open architecture 3. open source questions @conduce paul.saunders@conduce.net
  69. 69. MRO software in the future a shift towards openness 1. open data 2. open architecture 3. open source questions @conduce paul.saunders@conduce.net
  70. 70. MRO software in the future a shift towards openness 1. open data 2. open architecture 3. open source questions @conduce paul.saunders@conduce.net
  71. 71. MRO software in the future a shift towards openness 1. open data 2. open architecture 3. open source questions @conduce paul.saunders@conduce.net
  72. 72. MRO software in the future a shift towards openness 1. open data 2. open architecture 3. open source questions @conduce paul.saunders@conduce.net
  73. 73. MRO software in the future a shift towards openness 1. open data 2. open architecture 3. open source questions @conduce paul.saunders@conduce.net
  74. 74. MRO software in the future a shift towards openness 1. open data 2. open architecture 3. open source questions @conduce paul.saunders@conduce.net
  75. 75. MRO software in the future a shift towards openness 1. open data 2. open architecture 3. open source questions @conduce paul.saunders@conduce.net
  76. 76. MRO software in the future a shift towards openness 1. open data 2. open architecture 3. open source questions @conduce paul.saunders@conduce.net
  77. 77. MRO software in the future a shift towards openness 1. open data 2. open architecture 3. open source questions @conduce paul.saunders@conduce.net
  78. 78. MRO software in the future a shift towards openness 1. open data 2. open architecture 3. open source questions @conduce paul.saunders@conduce.net
  79. 79. MRO software in the future a shift towards openness 1. open data 2. open architecture 3. open source questions @conduce paul.saunders@conduce.net
  80. 80. MRO software in the future a shift towards openness 1. open data 2. open architecture 3. open source questions @conduce paul.saunders@conduce.net
  81. 81. MRO software in the future a shift towards openness 1. open data 2. open architecture 3. open source questions @conduce paul.saunders@conduce.net
  82. 82. MRO software in the future a shift towards openness 1. open data 2. open architecture 3. open source questions @conduce paul.saunders@conduce.net
  83. 83. MRO software in the future a shift towards openness 1. open data 2. open architecture 3. open source questions @conduce paul.saunders@conduce.net
  84. 84. MRO software in the future a shift towards openness 1. open data 2. open architecture 3. open source questions @conduce paul.saunders@conduce.net
  85. 85. MRO software in the future a shift towards openness 1. open data 2. open architecture 3. open source questions @conduce paul.saunders@conduce.net
  86. 86. barriers to mass collaboration laughable belief #1: mass collaboration benefits OEMs not operators questions @conduce paul.saunders@conduce.net
  87. 87. barriers to mass collaboration laughable belief #2: an operator’s data is valuable & shouldn’t be shared questions @conduce paul.saunders@conduce.net
  88. 88. MRO software in the future what else is coming? questions @conduce paul.saunders@conduce.net
  89. 89. MRO software in the future augmented reality questions @conduce paul.saunders@conduce.net
  90. 90. word lens questions @conduce paul.saunders@conduce.net
  91. 91. plane finder AR questions @conduce paul.saunders@conduce.net
  92. 92. line engineer AR questions @conduce paul.saunders@conduce.net
  93. 93. line engineer AR questions @conduce paul.saunders@conduce.net
  94. 94. line engineer AR questions @conduce paul.saunders@conduce.net
  95. 95. line engineer AR questions @conduce paul.saunders@conduce.net
  96. 96. line engineer AR questions @conduce paul.saunders@conduce.net
  97. 97. MRO software in the future augmented reality metadata tagging questions @conduce paul.saunders@conduce.net
  98. 98. MRO software in the future augmented reality metadata tagging socialisation of data questions @conduce paul.saunders@conduce.net
  99. 99. MRO software in the future augmented reality metadata tagging socialisation of data more cloud based software questions @conduce paul.saunders@conduce.net
  100. 100. MRO software in the future augmented reality the semantic web metadata tagging socialisation of data more cloud based software questions @conduce paul.saunders@conduce.net
  101. 101. MRO software in the future lighter weight software augmented reality XaaS function specific software less bloated software the semantic web less features metadata tagging more mobility shorter development life cycles socialisation of data device specific applications integration easier more cloud based software questions @conduce paul.saunders@conduce.net
  102. 102. MRO software in the future hardware no longer matters lighter weight software augmented reality XaaS function specific software web 3.0 less bloated software the semantic web service oriented architecture less features metadata tagging more mobility enterprise 2.0 shorter development life cycles tablets socialisation of data open source device specific applications integration 3 easier android social media generation become users geo-location everything more cloud based software html5 & css3 questions @conduce paul.saunders@conduce.net
  103. 103. MRO software in the future questions @conduce paul.saunders@conduce.net
  104. 104. MRO software in the future questions @conduce paul.saunders@conduce.net
  105. 105. MRO software in the future questions @conduce paul.saunders@conduce.net
  106. 106. if somebody says to you ‘that is impossible’ questions @conduce paul.saunders@conduce.net
  107. 107. you should understand their statement to mean….‘according to my verylimited experience andnarrow understanding ofreality, that’s very unlikely’ questions @conduce paul.saunders@conduce.net
  108. 108. your questions
  109. 109. more information…http://blog.conduce.nethttp://uxmag.comhttp://thinkvitamin.comREWORK by Jason Fried & David Heinemeir HanssonThe Visual Display of Quantitative Information by Edward Tuftethanks to http://lostandtaken.com/ for all the background images

×