Download to read offline
Uploaded byInfinIT - Innovationsnetværket for it
Platformsstrategi for SW & HW udvikling
John Kaasgaard of Grundfos presented on the company's domains, platforms, and architecture. He discussed past and present activities around hardware and software platforms, strategies for modularization, scalability, and supplier relationships. He outlined Grundfos' transition to a more structured architectural approach with standardized domains and platforms to improve flexibility, scalability, and cost-efficiency while maintaining capabilities.
More Related Content
Similar to Platformsstrategi for SW & HW udvikling
More from InfinIT - Innovationsnetværket for it
Platformsstrategi for SW & HW udvikling
- 1. John Kaasgaard Presentation ofGrundfos Domains, Platforms and Architecture. Past and present activities, methods (shown overall – not detailed) • 15.10 Platformsstrategi for SW & HW udvikling v. John Kaasgaard, Grundfos • HW & SW platforme • Strategier og tanker, modularisering, kombinatorik, skalerbarhed, test, 2’nd source & udskiftbarhed • Leverandørsamarbejde, forhandlinger 15.50 Opsamling 1 5/22/2017 (c) Grundfos A/S
- 2.
- 3. Supplier NDA Maintenance Costs Make or Buy? Various considerations 3 5/22/2017 (c) Grundfos A/S
- 4. Why make ityourself ? Why buy in ? Process and cont. monitoring to keep focus 4 5/22/2017 (c) Grundfos A/S
- 5.
- 6.
- 7.
- 8.
- 9.
- 10.
- 11.
- 12.
- 13.
- 14.
- 15. • 15.10 Platformsstrategifor SW & HW udvikling v. John Kaasgaard, Grundfos • HW & SW platforme • Strategier og tanker, modularisering, kombinatorik, skalerbarhed, test, 2’nd source & udskiftbarhed • Leverandørsamarbejde, forhandlinger 15.50 Opsamling 15 5/22/2017 (c) Grundfos A/S
- 16. What to come? Past understanding and architecture, domains, platforms, BB The last few years activities forming a more solid ‘real’ architecture … Current scope and understanding on product- & system doamins and architectures 16 5/22/2017 (c) Grundfos A/S
- 17. A few wordson the initial work on architecture, domains and building blocks … 17 5/22/2017 (c) Grundfos A/S
- 18. Take-1 I startedthe BB team in ~2008 Many years of forming and finding best practices was collected and formalized. Introducing Unit testing, CC/CQ, system testing using MCTAP later product testing SeqSap. Take-2 Demands for future advanced communication and wish for IoT kicked the process for real architecture based work broadly founded in the dev org! Everything/everyone was pulled in and applied features, definitions, and demands for the future. Lead to a way-to-big reference designs, less scalable than expected and far from cheap! But we had Small-Medium-Large and Xtra-Large platforms! Take-3 Shortly after we did the same work again. Less people more structural architectural work. Now focusing much more or architecture parts and process. Now we could make platforms that could compete with lowcost, being flexible, scaleable, … Take-4 Requirement management top-down and work with external universities and ERFA groups make introduction of full system element and functional requirements in eg. Doors the new way(s) 18 5/22/2017 (c) Grundfos A/S
- 19. Huge organization, very de-centralizedoperations, many kingdoms … Each dept har their own HW & SW guy’s Very product focused 19 5/22/2017 (c) Grundfos A/S
- 20. Some few old-timeppt… 20 5/22/2017 (c) Grundfos A/S
- 21. What is aplatform ? What is a technology platform ? What is a product platform ? New words – new concepts – new tools – new ways of working 21 5/22/2017 (c) Grundfos A/S
- 22. Organization and usingCC lead to understanding other stuff that libraries Focus on CC – orchestra & formalizing the ‘architecture’ We now have components Many forms of the phrase - a ‘platforms’ Product, domain and architecture … 22 5/22/2017 (c) Grundfos A/S
- 23. Platforms and technologiesforms domains Different business areas give diff domains uses diff platforms But basically pulling the same components into the platform We had Black and Red pumps solutions Each dept. arguing for the same – they were very different ☺ All though the both moved water from A to B (view on this though changed over the years as the organization changed) 23 5/22/2017 (c) Grundfos A/S
- 24. What is acomponent … 24 5/22/2017 (c) Grundfos A/S
- 25. We formed ‘architecture’by setting requirements to the the implementations … Several points still very valid and in use (enforced) today … 25 5/22/2017 (c) Grundfos A/S
- 26. 2010 De-centralized centralized sw 2012 Hwand mech follows Though not all the way on requirements & architecture … 26 5/22/2017 (c) Grundfos A/S
- 27. ~4 years ago Demandsfor new architecture lead to assembling many people, many requirements, all- singing-all-dancing scenarios At this time the Org also said – all product must be able to communication (not full IoT but close) Requirement handling for both HW and Mech was in focus. (sw already there) In parallel: Develop Organization(s) puts lots of effort in handling requirements 27 5/22/2017 (c) Grundfos A/S
- 28. Thinking more onthe resulting platforms than on the actual architecture Got S + M + L + XL platforms – suitable for controller & pumps A big architecture – very configurable - all singing all dancing Difficult to handle small changes on the interfaces 28 5/22/2017 (c) Grundfos A/S
- 29. We were tolate thinking to little on resulting pricing(when instantiating arch into products) Cost(s) went up because of flexibility more than scalability 29 5/22/2017 (c) Grundfos A/S
- 30. We had torethink the set-up again while results were not satisfactory We took a more architectural approach with the same requirements We looked at various prioritized cost drivers - Cost - scalability - Flexibility - Adding hw/sw brings in the cost - New comm tech - Tool base & testing 30 5/22/2017 (c) Grundfos A/S
- 31. Now a moreflexible architecture and resulting platform(s) was made supporting very low cost products as well as high end within same architecture… You can also say that ‘all-singing-all-dancing’ went out of the architecture! But you can all ways add later… We also ‘agreed’ on those wanting extra pays the bill! No such thing as free lunch! The architecture resulted in more flexible and saleable capabilities on a platform 31 5/22/2017 (c) Grundfos A/S
- 32.
- 33.
- 34. Grundfos has fromthe ‘early’ days been looking at the AUTOSAR RTE solutions. Though not fully full filling our needs, it though did provide a firm star on the sky! AUTOSAR standardization was a closed group only for automotive makers – industries was no allowed access. This has changed the last years! Over the years we have slightly modified and changed part of the RTE, applying various generation locally. RTE V1, RTE V2 and now RTE V3 … Data was first located in the RTE layer as a traditional DBB (Data Black Board). Later (today) data is again decentralized and owned by the provider of the data point. Using Publish/subscribe functions to gain access. As well as now working with providing locking mechanisms and more … 34 5/22/2017 (c) Grundfos A/S
- 35. Key words oncore tech. What differs you from the marked? What is your key competences ? Where is your gold ? 35 5/22/2017 (c) Grundfos A/S
- 36. Know your technologies… Here the variations of eg. protocols supported make sure all technology areas are - Identified - Organized - Individually addressed and - separated. 36 5/22/2017 (c) Grundfos A/S
- 37. Example on focus… External and internal communication channels can/will separate the water … So you may have with - algorithm, - special applications, - various control elements, - diff HMI, … 37 5/22/2017 (c) Grundfos A/S
- 38. Important: Flexibility makes sureyou practically can pick any component/module for any system. ‘Make or Buy’ is an important strategical focus area. Layered architecture ease the usage, the update and interaction with 3’rd part software. 38 5/22/2017 (c) Grundfos A/S
- 39.
- 40. Example on aninstance of the architecture Scalabilities and moving feature from one platform to another is possible having good architecture! Here a full blown example … Actual 3 boards: - BE (Back-End) motor control - Main board sensor interface, protocols, communication, intelligence/controls, main appl - HMI FE or (front end) 40 5/22/2017 (c) Grundfos A/S
- 41. What’s the benefitsfrom all the activities - Performance - Scalability - Up: getting performance or - Down: cost reduction) - Testability - Service- & maintenance - Customer adding features And many more … 41 5/22/2017 (c) Grundfos A/S
- 42. Adding requirement managementtop-down really changes the way of organizing and maturing, working on making products <missing parts here> 42 5/22/2017 (c) Grundfos A/S
- 43. Tools today areCC/CQ – though in the process of moving to GIT/Jira We have been looking at the automotive AUTOSAR RTE - Though being a industrial company and not Automotive we could not participate in standardizations, inside meetings and many many more areas … Software is organized in 3(4) primary layers - +80 core basic components - +30 primary/core applications - +nn system applications - Display/presentation layer 43 5/22/2017 (c) Grundfos A/S
- 44. HW, SW &Mech has release trains delivering continuously 44 5/22/2017 (c) Grundfos A/S
- 45.
- 46.
- 47. A product canbe thought of as functional elements These are NOT at description of the physical (tangible) elements of the product… ..but a description of the functions that the physical elements shall provide 47 5/22/2017 (c) Grundfos A/S
- 48.
- 49.
- 50. Why domains areimportant 50 5/22/2017 (c) Grundfos A/S
- 51.
- 52. API: Application interface SRA:System Reference Architecture DSS: Digital Systems Solutions ED: Electronic Development (HW+SW) MD: Mechanic Development http://www.incose.org/Home http://www.incose.org/docs/default-source/ProductsPublications/a-complexity-primer- for-systems-engineers.pdf?sfvrsn=0 52 5/22/2017 (c) Grundfos A/S
- 53.
- 54.
- 55.
- 56.
- 57.
- 58.
- 59.
- 60.
- 61.
- 62.
- 63.
- 64.
- 65.
- 66.
- 67.
- 68. ED = ControlBox on/inside a pump and general controllers 68 5/22/2017 (c) Grundfos A/S
- 69.
- 70.
- 71.
- 72.
- 73.
- 74.
- 75.