A model for designing product-service systems using functional analysis and agent based model Author: Nicolas Laboratory, Grenoble universities – INPG,

Slides:



Advertisements
Similar presentations
Definitions Innovation Reform Improvement Change.
Advertisements

Identify Problems, Planning Objectives and Constraints.
Chapter 13: Organizational Innovation and Change
How to Map a Sales Process That Creates Value for Customers! July 2003.
Abstraction Lecture-4. ADT example: London Underground Map.
13-2 Defining Leadership “The ability to influence through communication the activities of others, individually or as a group, toward the accomplishment.
Using the Crosscutting Concepts As conceptual tools when meeting an unfamiliar problem or phenomenon.
Presented by: Thabet Kacem Spring Outline Contributions Introduction Proposed Approach Related Work Reconception of ADLs XTEAM Tool Chain Discussion.
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
OASIS Reference Model for Service Oriented Architecture 1.0
Software Testing and Quality Assurance
IMS1805 Systems Analysis Topic 3 (revisited and continued): Doing analysis – a ‘soft’ systems perspective.
Analysis Concepts and Principles
9 1 Chapter 9 Database Design Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
1 Requirements Analysis and Specification Requirements analysis.
System Engineering Instructor: Dr. Jerry Gao. System Engineering Jerry Gao, Ph.D. Jan System Engineering Hierarchy - System Modeling - Information.
University of Jyväskylä – Department of Mathematical Information Technology Computer Science Teacher Education ICNEE 2004 Topic Case Driven Approach for.
DATA FLOW DIAGRAMS IT 155.
Trier 2007 Declan Fleming Department of Marketing Topic 1: Marketing Dynamics.
Certified Business Process Professional (CBPP®) Exam Overview
Introduction to Organization Theory Dr. Upul Abeyrathne, Dept. of Economics, University of Ruhuna Matara.
Architectural Design Establishing the overall structure of a software system Objectives To introduce architectural design and to discuss its importance.
Assignment 2 Case Study. Criteria Weightage - 60 % Due Date – 11 th October 2012 Length of Analysis – 2500 words Leverage % including appendices,
Project Management Body of Knowledge PMBOK
The Knowledge Resources Guide The SUVOT Project Sustainable and Vocational Tourism Rimini, 20 October 2005.
Exploration into the barriers and obstacles constraining diffusion and adoption of renewable energy solutions Saskia Harkema and Mirjam Leloux Wittenborg.
Chapter 5 Product Specifications. Learning Objectives How to translate subjective customer needs into precise target specs? How could the team resolve.
MANAGING STRATEGY INTRODUCTION TO STRATEGIC MANAGEMENT.
A case study of Quality Standards implementation in TASNEE Company ISO 9001: 2000, ISO 14001:2004 & OHSAS By Abdulgader Alharthi.
On Roles of Models in Information Systems (Arne Sølvberg) Gustavo Carvalho 26 de Agosto de 2010.
Chapter 4 Requirements Engineering
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
Requirements Analysis
Information Systems in Organisations System Development: The Environment.
Intelligent Cargo in Efficient and Sustainable Global Logistics Operations WP5 – Open End-to-End Pilots Implementation Jose Gato Luis –
Architecture Business Cycle
1M.Sc.(I.T.), VNSGU, Surat. Structured Analysis Focuses on what system or application is required to do. It does not state how the system should be implement.
Chapter 11: Strategic Leadership Chapter 8 Production and operations management.
Sustainability indicators for Small and Medium- sized Enterprises (SMEs) in the transition to provide Product-Service Systems (PSS) Erik Sundin 1, Elin.
Through-life Engineering Services
Module 4: Systems Development Chapter 12: (IS) Project Management.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Software Engineering Saeed Akhtar The University of Lahore Lecture 7 Originally shared for: mashhoood.webs.com.
Lecture 7: Requirements Engineering
1 Advanced Software Architecture Muhammad Bilal Bashir PhD Scholar (Computer Science) Mohammad Ali Jinnah University.
Software Engineering. Introduction Objective To familiarize students to the fundamental concepts, techniques, processes, methods and tools of Software.
Positive and Negative Aspects of Conflict Positive Can bring about necessary change Negative Cause stress Reduce productivity May cause harm to the organization.
Investigation on the Library Robot “Alice” in an enterprise Lin Yuan.
Author : A.R Tan,M. M. Andreasen and D. Matzen Teacher : Soe-Tsyr Daphne Yuan Presenter : Liao, Ting-Yi CONCEPTUALISATION OF PRODUCT/SERVICE-SYSTEMS THROUGH.
Measuring Performance Why Measures:- What can not be measures - it cannot be managed.
Communicating Marketing Research Findings
The Second Annual Medical Device Regulatory, Reimbursement and Compliance Congress Presented by J. Glenn George Thursday, March 29, 2007 Day II – Track.
Requirement Engineering
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
UTA/ARRI. Enterprise Engineering for The Agile Enterprise Don Liles The University of Texas at Arlington.
Alex Ezrakhovich Process Approach for an Integrated Management System Change driven.
Value network analysis for complex service systems: Author : Juite Wang Jung-Yu Lai Li-Chun Hsiao Professor : Soe-Tsyr Daphne Yuan Presenter : Po-Wei Chiang.
Software Engineering Process - II 7.1 Unit 7: Quality Management Software Engineering Process - II.
SECURE TROPOS Michalis Pavlidis 8 May Seminar Agenda  Secure Tropos  History and Foundation  Tropos  Basics  Secure Tropos  Concepts / Modelling.
Model Checking Early Requirements Specifications in Tropos Presented by Chin-Yi Tsai.
Chapter 2 Bring systems into being April Aims of this Lecture To explain what is “System Life-Cycle” To understand the systems engineering process.
Procurement- Lecture 3 Customer service and logistics
Introduction to Methods Engineering
Fundamentals of Information Systems, Sixth Edition
TechStambha PMP Certification Training
Level 1 Level 1 – Initial: The software process is characterized as ad hoc and occasionally even chaotic. Few processes are defined, and success depends.
Chapter 20 Object-Oriented Analysis and Design
[Authors] [Affiliation]
Writing Business Reports and Proposals
Information system analysis and design
Presentation transcript:

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

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

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.

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.

The background of Vélo'v example

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

The proposed approach for PSS development and Vélo‘v example

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

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.

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

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.

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

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.

Scope Model Flow Model

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

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 Flow Model

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. Cost for operating company(-) Incentive to use the service (+) Huge numbers of stations↑↑ Few stations↓↓

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

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)

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.

Outer environment Outer environment Product Product

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

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)

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

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

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.

Outer environment Outer environment Product Product

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

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

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.

Thank you for listening!!