Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Icp 3273-the iiot understanding designing and developing the bigger picture v2

515 views

Published on

Understanding the role of Systems engineering in the development of IOT architectures.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Icp 3273-the iiot understanding designing and developing the bigger picture v2

  1. 1. © 2015 IBM Corporation The Industrial Internet of Things Understanding ,Designing & Developing the bigger picture Dr. G.J Bleakley & A whitfield graham.bleakley@uk.ibm.com, @BleakleyGJ adrian.whitfield@us.ibm.com
  2. 2. Headline Goes Here • Level 1 bullet • Level 1 bullet • Level 2 bullet • Level 2 bullet – Level 3 bullet 1
  3. 3. Agenda • What is public perception of the IOT ? • Public perception • High level overview of IOT example • Issues with the IOT • Washing machine example • Headline issues • What Industrialises the IOT ? • Need for systems of systems approach to develop IOT architectures • Need for a service based approach • Intro to the IIC • IIC framework • Mapping to UPDM (Autonomous city driving) • How can IBM help • UPDM to do high level architecture and business motivation • SysML tools to capture IOT specifications • Implementation technologies – IOT work bench to simulate and test out IOT architectures at the thing level – Blue Mix and Node Red to simulate IOT architectures at the cloud level – Rhapsody to generate code for the “Things” 2
  4. 4. Common perception of the Internet of Things 3 Source: IDC’s 2014 Internet of Things Survey Large Collection bulk of info Digital Information Security Households connect to the internet Collections of things RFID Connect to the cloud Everything to do with the internet All communications
  5. 5. What the IOT really is ? Connected car example 4 Constituent Devices Constituent Devices (Agents/Things) IoT Cloud Predictive Analytics Communication infrastructure • Designing and connecting devices • Adding intelligence at the appropriate levels • Design the back end systems • Analytics • Decision Making • Optimize the overall systems architecture • Understanding and using the information gathered Monetizing the information that you have gathered
  6. 6. Example “Connected Washing Machine” Perspective of white goods manufacturer • Reduce energy costs by connecting your washing machine to the internet • Let your washing machine decided when to go through its cycle based upon cheapest energy tariff ! 5 • Works for a few devices but not scaleable • Think of a city of 20 Million People (Seoul) • Applications like this can have powerful socio-economic effects • Go from Consumer to Industrial/Commercial domain External Power Companies Local Power Companies
  7. 7. “Connected Washing Machine” realistic example 6 1-Millions Washing Machines White Goods companies • Much more complex architecture • No single owner or beneficiary of the application • Complex set of partnership agreements • Highly federated and distributed • Need for the system to be engineered
  8. 8. 11 Unique challenges for the IIOT 7 • 1. Ownership - No one owns "all of it" ... • 2. Social, Pervasive and has to add value - no one is going to pay for a subscription to a service if it doesn’t • work very well, • offer value, or • fit into their lives without them having to really think about it • 3. Complexity and dependency magnified • 4. Security, safety and industry standards magnified • 5. Impact on development and implementation and testing – • Working with other partners to deliver complete solution. • Increases burden on development of (devices, infrastructure and services, etc). • Device, services, etc need to be upgradable (needs to service based). • Work either connected or not connected, be up 24/7, never fail, have redundancy (when safety implications), etc ... • 6. Time to market.
  9. 9. 11 Unique challenges for the IIOT • 7. Always on, always connected, has to always work without user interaction, • Consumers, users, and buyers of such systems will demand it ... e.g. turn the 311,000 traffic signals in the USA into smart traffic lights. We don’t want to have to manually maintain these? • 8. Highly diverse use cases • We can only begin to imagine what’s possible • 9. Traditional development practices don’t scale to these types of systems • 10. Foray of new business relationships -- that will need to be properly managed • 11. Volume of data that will need to be; • Managed • Analyzed, • Processed, etc. 8
  10. 10. What Industrialises the IOT ? • Use IOT technology to improve the way that social (health/local government), manufacturing and industrial organisations do business • Not directly about the consumer or customer but more about the business itself • Beneficaries are internal • Numerous examples • Break and repair to fault monitoring and predictive maintenance (Oil and Gas) – Improve oil-gas field producitvity – Reduce down time • GPS guided driving to Smart Cities route allocation to improve health – Reduce emissions in town – Improve health • Schedule vehicle servicing and issues raising to remote fault monitoring of vehicles and automated issue generation – Prevent defect propagation – Improve customer safety 9
  11. 11. The Industrial Internet Consortium (IIC) • Group of companies founded by IBM, GE, CISCO, Intel and AT&T • 1 year old, approx 120 member companies – HW companies – SW companies – Security – Cognition etc. • The intent is to provide forum to discuss • Industrial IoT technology and applications • Develop practical use cases and implement them as examples on test beds • Develop a Framework and Reference Architecture that can be used to describe the IIOT • The framework and reference architecture provide a way to think about Systems Engineering • Understand, Design and Develop these systems. 10
  12. 12. IIC Framework 11 Biz decision makers System Engineers Product Managers System Engineers Product Managers System Architects Architects Engineers Developers Integrators Deployment Operations Biz View A Model Another Model Usage View A Model Functional View Implementation View Implementation Viewpoint Functional Viewpoint Usage Viewpoint Business Viewpoint biz values, objectives & capabilities usage scenario/activiti es Functional decomp & structure Interfaces & interactions functional entities to technologies mapping
  13. 13. What tools do we have • Business View • Enterprise Architecture • Systems of systems modelling • Usage and Functional View • Systems engineering • Implementation View • Analytics • Software development – Embedded Software – Services • Cloud 12
  14. 14. Business View • UPDM and Rational Rhapsody • IIC Framework is simplified framework to allow people to think about developing IOT applications using Systems of Systems thinking • Layers and key concepts map to the Unified Profile for DoDAF and MODAF • Soon to be called the Unified Architecture Framework • OMG standard implemented in many tool • Business View maps to Capability or Strategic Views • Providing rationale and identify key capabilities • Usage View maps to Operational • What the system will be used for and the organisations involved in its usage • Functional and Implementation map to Systems View • How the system needs to do and how it can be implemented 13
  15. 15. Business Views • Capability Taxonomy • Sets the context for the architecture • Lets you think about what you are trying to achieve • Can be used to capture reqs and desired effects (MoEs) • Capability Dependencies • Widen the scope • Helps Identify commonly used capabilities – Reuse implementation
  16. 16. Usage Views • Operational Activity Model, Behavioral model that shows high level behaviour that helps realise the capability • Initiating the log on of the vehicle • Capturing initial position • Destination • Route planning ect. • Operation Resource Flows • Structural Model that shows how Performers interact • Shows interfaces between Traffic, Traffic Analysis and Traffic Control – Where flows cross swimlanes • Trace operational Activities to Capabilities
  17. 17. Functional View • Putting more detail into the analysis • Allocated to – Navigation – EngineControls – Traffic and PedestrianManagement – AutonomousRouteFollowing • Traceability back to the higher level
  18. 18. Systems Implementation  Systems Interfaces Description  Logical communication between system level resources  Resource interactions and data exchanges (not shown)  System equivalent of Operational Resource Flow  Resource Flow Description  Physical architectures shows things like  Communication networks  Communication Protocols (types of standards)  Reality is you need to think of Systems as a Service  Technology will change quickly  Need flexibility  Extendability
  19. 19. Detailed Implementation • Use Continuous Engineering to develop Embedded IoT applications using Rhapsody • Small targets for “Things” • Use simulation to verify correctness of solutions • Software can be ported to target • Raspberry PI • Arduino etc.
  20. 20. Implementing the Structure • IOT Work bench • Blue Mix • Node Red 19
  21. 21. Implementing the Analytics • Cognos • Maximo 20
  22. 22. Working on the Cloud • Blue Mix • Softlayer 21
  23. 23. Sample Pie Chart Sales 1st Qtr 2nd Qtr 3rd Qtr 4th Qtr 22
  24. 24. 0 1 2 3 4 5 6 Category 1 Category 2 Category 3 Category 4 Series 1 Series 2 Series 3 Sample Bar Chart 23
  25. 25. Color Palette 24
  26. 26. Divider slide
  27. 27. Notices and Disclaimers Copyright © 2015 by International Business Machines Corporation (IBM). No part of this document may be reproduced or transmitted in any form without written permission from IBM. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM. Information in these presentations (including information relating to products that have not yet been announced by IBM) has been reviewed for accuracy as of the date of initial publication and could include unintentional technical or typographical errors. IBM shall have no responsibility to update this information. THIS DOCUMENT IS DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY, EITHER EXPRESS OR IMPLIED. IN NO EVENT SHALL IBM BE LIABLE FOR ANY DAMAGE ARISING FROM THE USE OF THIS INFORMATION, INCLUDING BUT NOT LIMITED TO, LOSS OF DATA, BUSINESS INTERRUPTION, LOSS OF PROFIT OR LOSS OF OPPORTUNITY. IBM products and services are warranted according to the terms and conditions of the agreements under which they are provided. Any statements regarding IBM's future direction, intent or product plans are subject to change or withdrawal without notice. Performance data contained herein was generally obtained in a controlled, isolated environments. Customer examples are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual performance, cost, savings or other results in other operating environments may vary. References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services available in all countries in which IBM operates or does business. Workshops, sessions and associated materials may have been prepared by independent session speakers, and do not necessarily reflect the views of IBM. All materials and discussions are provided for informational purposes only, and are neither intended to, nor shall constitute legal or other guidance or advice to any individual participant or their specific situation. It is the customer’s responsibility to insure its own compliance with legal requirements and to obtain advice of competent legal counsel as to the identification and interpretation of any relevant laws and regulatory requirements that may affect the customer’s business and any actions the customer may need to take to comply with such laws. IBM does not provide legal advice or represent or warrant that its services or products will ensure that the customer is in compliance with any law.
  28. 28. Notices and Disclaimers (con’t) Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products in connection with this publication and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. IBM does not warrant the quality of any third-party products, or the ability of any such third-party products to interoperate with IBM’s products. IBM EXPRESSLY DISCLAIMS ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. The provision of the information contained herein is not intended to, and does not, grant any right or license under any IBM patents, copyrights, trademarks or other intellectual property right. • IBM, the IBM logo, ibm.com, Bluemix, Blueworks Live, CICS, Clearcase, DOORS®, Enterprise Document Management System™, Global Business Services ®, Global Technology Services ®, Information on Demand, ILOG, Maximo®, MQIntegrator®, MQSeries®, Netcool®, OMEGAMON, OpenPower, PureAnalytics™, PureApplication®, pureCluster™, PureCoverage®, PureData®, PureExperience®, PureFlex®, pureQuery®, pureScale®, PureSystems®, QRadar®, Rational®, Rhapsody®, SoDA, SPSS, StoredIQ, Tivoli®, Trusteer®, urban{code}®, Watson, WebSphere®, Worklight®, X-Force® and System z® Z/OS, are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at: www.ibm.com/legal/copytrade.shtml.
  29. 29. Thank You Your Feedback is Important! Access the InterConnect 2015 Conference CONNECT Attendee Portal to complete your session surveys from your smartphone, laptop or conference kiosk.

×