A model for designing product-service systems using functional analysis and agent based model

1. A model for designing product-service systems using functional analysis and agent based model Author: Nicolas Laboratory, Grenoble universities – INPG, France Teacher: Soe-Tsyr Daphne Yuan Presenter: Sally Wang

2. Agenda • Introduction • The background of Vélo'v example • The proposed approach for PSS development and Vélo‘vexample • An overall system analysis • Detailed design of PSS elements • Conclusion

3. Introduction

4. Introduction • In developed countries, more and more enterprises switch to provide service solutions from selling physical products. • This awareness of innovation and sustainability leads to the concept of PSS. • Analyzing the value of the PSS is the key issue. • The development of PSS will be created by using agent-based model and functional analysis while considering value services.

5. Introduction (Cont.) • Agent based model:enable designers to highlight the detail value and costs. • Functional analysis: is more a functions oriented representation. • Tools and representations enable engineering designers to highlight and characterize customers’ requirements and then to detail technical functions and solutions that will fulfill those requirements.

6. The background of Vélo'v example

7. Vélo'v • Since 2005 • A rental bike system • Move in the city • Charge for the use-time • Rent from one place, bring back to another place • Very popular in Lyon, France

8. The proposed approach for PSS development and Vélo‘vexample

9. The Proposed Approach For PSS Development • An overall system analysis • Customers’ needs analysis and people’s involvement • Flow Model, Scenario Model and Scope Model • Translation of requirements into external functions (=service functions) • The graph of interactors • Definition of the technical functions and of the corresponding solutions • FAST diagram and Functional Bloc diagram • Detailed design of PSS elements

10. Customers’ needs analysis and people’s involvement • It’s critical that all the involved agents find a balance between the value they receive and the costs they support. • Flow Model: represents the agents participating in the service. • Scenario Model: represents the properties of a service receiver and his behavior when receiving the service. • Scope Model: describes all the value and cost of a receiver in a specified range in the service.

11. The Scope Model will focus and study each relation in order to highlight values/costs of receiver. Flow Model do not participate in the service but only affects the service.

12. Customers’ needs analysis and people’s involvement • It’s critical that all the involved agents find a balance between the value they receive and the costs they support. • Flow Model: represents the agents participating in the service. • Scenario Model: represents the properties of a service receiver and his behavior when receiving the service. • Scope Model: describes all the value and cost of a receiver in a specified range in the service.

13. Cost • Value Scenario Model By describing a Scenario Model for each agent in Figure 2, designers could identify the associated value/cost as show in Table 1.

14. Customers’ needs analysis and people’s involvement • It’s critical that all the involved agents find a balance between the value they receive and the costs they support. • Flow Model: represents the agents participating in the service. • Scenario Model: represents the properties of a service receiver and his behavior when receiving the service. • Scope Model: describes all the value and cost of a receiver in a specified range in the service.

15. Flow Model Scope Model

16. The Scope Model will focus and study each relation in order to highlight values/costs of receiver. Flow Model do not participate in the service but only affects the service.

17. Flow Model Scope Model A: For operating company from Bicycle manufacturer C: For operating company from city hall D: For bicycler from operating company H: For operating company from people with vandalism

18. Scope Model • The aim of the designer is to enhance values while avoid costs. • All of these RSP will influence the choice and criteria of functions. • For example, reduce the cost for the bicycler relative to “moving to station”, there are must be some compromises between a huge numbers of stations and a too low distribution of stations.

19. The Proposed Approach For PSS Development • An overall system analysis • Customers’ needs analysis and people’s involvement • Flow Model, Scenario Model and Scope Model • Translation of requirements into external functions (=service functions) • The graph of interactors • Definition of the technical functions and of the corresponding solutions • FAST diagram and Functional Bloc diagram • Detailed design of PSS elements

20. Translation of requirements into external functions • In order to highlight customers’ requirements and external people who could have an influence on the PSS, graph of interactors will be used. • Designers have to identify and describe the outer environments that can have an influence or that are put in relation through the PSS. • Outer environment: • Agents identified in flow model. • “non-financial” agents influencing the PSS. (like climate, the other road-users)

21. Translation of requirements into external functions • The graph of interactors is used to express these needs that are service functions and constraints: • The interaction functions (IF): which correspond to the services provided by the product during the product life cycle. • The adaptation functions (AF): that reflect reactions, resistances or adaptations to elements found in the outside environment. • The constraints: are defined as a design characteristic, effort or provision for design, which is made compulsory or forbidden for whatever reason.

22. Outer environment • Product

23. The Proposed Approach For PSS Development • An overall system analysis • Customers’ needs analysis and people’s involvement • Flow Model, Scenario Model and Scope Model • Translation of requirements into external functions (=service functions) • The graph of interactors • Definition of the technical functions and of the corresponding solutions • FAST diagram and Functional Bloc diagram • Detailed design of PSS elements

24. Definition of the technical functions and of the corresponding solutions • Engineering designers cannot directly find technical solutions related to the external functions. • External functions analysis: characterize the function expected by the customer. • Internal functions analysis: used to fulfill customers’ requirements and describe the core of PSS. • First, we need to conduct internal functional analysis which supported with • FAST diagram (Function Analysis System Technique) • FBD (Functional Bloc Diagram)

25. FAST diagram • Enables designers to detail service functions into technical functions and then to imagine different solutions. • Solution can be: • Physical objects • Technical service units

26. Rectangle: • physical objects. • Hexagon: • the technical service units.

27. Functional Bloc Diagram (FBD) • BUT, links between physical objects or technical elements are also important. • The aim of the FBD is to map these interactions. • It enables designers to develop and optimize the scenario for all service activities.

29. Outer environment • Product

30. Rectangle: • physical objects. • Hexagon: • the technical service units. DB4 DB1 DB2 DB3 Design buckles (DB) represent the technical functions necessary that ensure the realization of the external functions to satisfy the customers’ needs.

31. The Proposed Approach For PSS Development • An overall system analysis • Customers’ needs analysis and people’s involvement • Flow Model, Scenario Model and Scope Model • Translation of requirements into external functions (=service functions) • The graph of interactors • Definition of the technical functions and of the corresponding solutions • FAST diagram and Functional Bloc diagram • Detailed design of PSS elements

32. Conclusion • Whatever the adopted point of view to develop PSS is (system or product), the new added value of such service is the key issue. • The method in this paper enables designers to detail values and costs provided by the PSS while considering the functions that will fulfill the expected requirements. • Future researches will concern a more detailed definition of the PSS value integrating environmental aspects and specific tools that could help designers to define the final solution.

33. Thank you for listening!!