Interoperable Open Architecture Primer


Published on

Published in: Business, Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Interoperable Open Architecture Primer

  1. 1. IOAUSA 2013Interoperable Open ArchitecturePrimerRTI, Real-Time Innovations, RTI Data Distribution Service, and Connext are registered trademarks or trademarks of Real-Time Innovations, Inc. All other trademarksused in this document are the property of their respective owners. All rights reserved.© 2013 RTI
  2. 2. Agenda• Introductions• What Changes in the Defense Marketdoes IOA focus on?• What is IOA – Objectives• How it Differs from OA• History of IOA Event to Date• IOA USA 2013
  3. 3. Key Changes in the DefenseMarket that IOA focuses on• USA – Sequestration– Threat of 10%+ cut in DOD Budgets• European Economic Woes– UK MOD $1B cut 2013-15Global Defense support requirements are notreducing – in fact they are increasing – ArabSpring – Pakistan instability – ChinaSuperpower growth
  4. 4. Signs of Change in ProcurementStrategyThe only way to address the budget issueis to rethink procurement strategy
  5. 5. The Big Cost in DefenseSpending?• Clue – the supply chain is referred to asSystem Integrators for a reason– Big metal is relatively cheap• Putting it together is very expensive– High integration costs, mostly software• Systems are effectively closed– Not technically -> commercially• Maintenance and logistics lock-in– Proprietary Integration technology guarantees allthis business has to flow to the original supplier
  6. 6. Integration = $B’s
  7. 7. The Integration Cost Multipliersfor Defense Procurement• Multiple suppliers– Build similar systems (planes, ships, vehicles etc)differently• Different countries build systemsdifferently– A significant integration issue in coalitionoperations• The legacy system problem– Old systems use old integration technology– New systems seek to reduce cost through moreadvanced integration technologies
  8. 8. Government’s Needs• Increased affordability– Especially through life• Faster deployment– From requirement to operational theater• Increase innovation and technologyadoption capability
  9. 9. The Warfighter NeedInteroperabilityas if everything made by one supplier
  10. 10. Interoperability• If all defense systems were architectedto be INHERENTLY INTEROPABLE– Massive $B savings in development costs– Massive $B savings in integration costs– Massive $B savings in logistics costs• AND– The warfighter would get faster access tolower cost technology, products and warfighting capability
  11. 11. Defense Procurement Shifting$$ $$
  12. 12. To This$$
  13. 13. Proof Points of Change• IOA programs– Open Group - FACE– US DoD UCS– MOD GVA– EDA FICAPS– US Army COE– NATO IST-090– Spanish Army Soldier support– Others…..
  14. 14. What is Interoperability?• Strangers meet, can converse if samelanguage– Can exchange complex ideas– But imagine you are at a sw convention of geeks,its still another language to some people• They have a supplemental dictionary of terms theyunderstand• So successful interoperability is abouthaving a common dictionary– But that’s not enough either
  15. 15. What is Interoperability?• We use voice to talk– Systems need to be architected upon acommon methodology in order to understandone another• But humans convey additional meaning– Shout, whisper, body language– Can Computers do the same?
  16. 16. InteroperabilityAt the end of the day it’s:“Do I understand you?”Interoperability has to IncludeSemantic Context in Communication
  17. 17. Where is Interoperability Built in?• In the non-functional system architecture– The glue software that enables two independentlydeveloped ‘functional’ applications to talk andexchange information successfully– Defined through a common dictionary of datadefinitions that all the systems use• One ‘data’ language for all DOD systems• Includes semantic context• Defined and owned by the DOD not the supply chain
  18. 18. Achieving InteroperabilityInteroperabilityBusinessModels
  19. 19. IOA• The focus on Interoperability is thecornerstone of IOA• IOA is where SI’s can align with DefenseProcurement to address the economicissue• IOA is where the warfighter can see asolution to his deployment integrationneeds• IOA is enabled by advances in non-functional system architecture technology
  20. 20. Differences to OA• OA has been hijacked by Industry– It always had interoperability as a goal butindustry undermined it• OA now equates to use of COTShardware and Open Standards software– COTS reduces metal costs but that’s notwhere the big $$’s are– Open Standards does not necessarily deliversystems interoperability
  21. 21. IOA 2011 positive’s• Brought key IOA protagonists togetherfor the 1st time– 1st time MOD and DOD exchanged ideas andviews on how to achieve IOA• Program managers realized theysought the same benefits• The system architects realized theirtechnology enablement approach waseffectively the same
  22. 22. IOA 2011 open issues• System Integrators were highlyskeptical– They were only peripherally ‘in the loop’– for some it was an unpleasant wake up call• There was no clear understanding ofwhat Interoperability was– Often confused with Open Systems,modularity, integratability, componentizationetc
  23. 23. IOA 2012 positive’s• Greater commonality of understanding whatInteroperability is and why its an importantfocus• Start of shift from technology enablingdiscussion towards procurement processchange discussion• Supply chain ‘just’ starting to shift fromskeptical to believers• Core Early Adopters starting to align and co-ordinate• US DoD taking a global lead
  24. 24. IOA 2012 open issues• Concerns of how to secure an openinteroperable architecture• European slow down on resourcingthis fundamental shift
  25. 25. IOA 2013• Creating an Affordable Future forDefence– Sharing best practice in defense procurementstrategy– Speeding technology adoption for thewarfighter– Enhancing Innovation insertion– Creating an agile procurement methodologyfor the modern ‘asymmetric’ combat world