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.

Dynamic HMI Design with Apps-based System in Mobile Machines

411 views

Published on


Learn more: http://solutions.parker.com/Prodisplay

Designing a machine HMI can be very challenging. The scope of the development project is huge covering several elements. In response to rapidly evolving market trends, software solutions should be flexible and fast. Machine manufacturers are trying to improve operator convenience, but integration of multiple user interfaces is very difficult.
The answer to these HMI challenges is an apps-based platform, which hides the complexity and offers an easy flow for your software development. It enables the integration of 3rd party applications and parallel, independent development of the machine HMI’s various functionalities. Read more about how Parker Hannifin’s apps-based system can be utilized in HMI software development. Parker’s Pro Display product family offers an intelligent platform to design a dynamic user interface for your mobile machine.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Dynamic HMI Design with Apps-based System in Mobile Machines

  1. 1. Tommi Forsman Principal Engineer, Electronic Controls Dynamic HMI Design with Apps- Based System in Mobile Machines
  2. 2. Agenda • Challenges with HMI (Human Machine Interface) design • Apps-based system • App UI (User Interface) and layout design • Sharing the screen with multiple apps • Widget framework • Building blocks and style sheet • User permissions • Application service framework • Application permissions • Application deployment • Application operation • Summary of apps-based system 2
  3. 3. Challenges with HMI Design To develop can be laborious and complex To maintain can be challenging To evolve with market trends is very hard To integrate is difficult 3
  4. 4. Apps-Based System App UI (User Interface) design 4 APP Look and feel Restricting content and access Communicating with other apps Secure app deployment Operation
  5. 5. App UI and Layout Design • Divide UI into own functional regions • Design the UI proportionally to available size • Rearrange the layout to available space 5
  6. 6. Sharing the Screen with Multiple Apps To see information from multiple apps at the same time, the foreground view should be able to divide in sections. 6 APP 1 APP 2 APP 3
  7. 7. Sharing the Screen with Multiple Apps • Divide the foreground with multiple apps • Allow apps to control the split screen • Apps with high priority can overlay on top of foreground apps (ie. alarm messages) 7
  8. 8. Widget Framework When the split screen is not enough to have all the required information displayed, a widget framework is needed. It allows applications to encapsulate small UI entities as a widget. 8 APP 1 APP 2 APP 3
  9. 9. Widget Framework 9 VALUE5 X X X X VALUE5 WIDGET 5 WIDGET 3WIDGET 1 Widgets can be informative (gauge or minimized app UI such as ISOBUS UT) or interactive (switches). WIDGET 4 WIDGET 6 VALUE1 VALUE2 VALUE1 VALUE2 WIDGET 2 Other apps can utilize widgets from the system Dynamic creation of widgets runtime Apps publish widgets in the system
  10. 10. Building Blocks and Style Sheet The platform style sheet enables developers to customize main UI building blocks’ look-n-feel in different levels: 10 Scaling Custom design Colors & fonts Design aspects
  11. 11. User Permissions When the app content need to be different for each type of users, the apps should be able to define their user permissions. 11 APP
  12. 12. User Permissions • Apps define own user permissions • One app to manage user accounts and user groups • Adaptation of new permissions 12
  13. 13. Application Service Framework Applications need to be able to communicate with each other, as well as share information and functionalities. 13
  14. 14. Application Service Framework • Apps can provide services to the system • Apps can subscribe these services from the system • The service interface and context should be declared 14
  15. 15. Application Permissions • App permissions for critical system functionalities (specially when working with 3rd party suppliers) • App developer simply declares needed app permissions 15
  16. 16. Application Deployment • All permissions are reviewed during app validation process • The deployment package defines all app dependencies • Apps are certified / encrypted by the system administrator 16
  17. 17. Application Operation • Apps should have operational and transitional states, to enable more flexible and dynamic system • Apps should be isolated from each other • System administrator can define initial apps which are loaded first 17 21 ! 3
  18. 18. Summary of Apps-Based System 18 Dynamic operation of apps Separate machine functionality into own apps Intelligent deployment of apps Integration of 3rd party and commercial apps Independent development and optimization of apps
  19. 19. Principal Engineer, Electronic Controls Parker Hannifin Manufacturing Finland Oy Lepistönkatu 10 • 30100 Forssa • Finland More information: http://solutions.parker.com/ProDisplay 19 Tommi Forsman

×