Test of 3rd Party Software at Grundfos

•Jens Lyngsoe•Software Developer•jlyngsoe@grundfos.com

Agenda

• IntroductionTest of 3rd party software (4 examples of what we have been

doing)• MODBUS protocol stack• Premptive OS – Segger EMBOS• PLC with development environment• Integrated operating system and development environment

Introduction to Grundfos

•Pumps and pump systems•16k employes world wide•5k5 employes in DK•600 in R&D in DK

•Company vision: 75k people in 2025

Grundfos Products•All market segments: HVAC, Water Supply, Waste Water, Industry, Dosing

Global R&D

•Electronic developers world wide

Hardware Software

Denmark 15 40

India 0-1 15

China 2 1

USA 1 1

France 3 4

Software Development Overview

Distribution of people in sw projects:

SW Projects

0

5

10

15

20

25

30

35

40

45

1 2 3 4 5 6 7 8 9 10

No. of developers / project

pro

ject

dis

trib

uti

on

[%

]

Key Objectives of Grundfos Software Development

• Small projects (1-7 persons)• Focus on quality rather than time• No dedicated testers• Software testing is integrated in the software development

proces• Embedded software• Homegrown OS (scheduler)• Homegrown datacommunication protocol

Test of 3rd party software(4 examples of what we have been

doing)• Premptive OS – Segger EMBOS• PLC with development environment• Integrated operating system and development environment• MODBUS protocol stack

Premptive OS – Segger EMBOS

What we wanted:• Graphics library• Preemptive multitasking• TCP/IP stack

Premptive OS – Segger EMBOS

What happened:• Supplier qualification• New MCU platform – 2 bugs found• Qualification test – listbox• Pc platform• Support• TCP/IP stack

PLC with development environment

What we wanted:• Platform for pump controllers• Flexible and scalable system

What happened:• Major partner – full confidence• Extensive changes to software• Testing: Review of spec.’s, test spec.’s

Integrated operating system and development environment

• For LONworks• Echelon operating system• Fast time to market for user application• Hardware integration• Development environment integration

What happened:• No faults found• Smooth integration creates confidence• Test: None specific to OS

MODBUS protocol stack

Background:• Addition to proprietary protocol stack• Homegrown version• Payd for version

What happened:• Test: protocol end-to-end as part of acceptance testing• No bugs found

Conclusion

• Confidence in supplier is the basis• We don’t want extra work – that’s a major reason for choosing 3rd

party suppliers in the first place• Review / overview of documentation• Small and fast initial test• Problems fastly creates a sense, that everything needs to be tested