Development of integrated design methodology for various types of product- service systems Author: Tuan A. Tran and Joon Y. Park – DGU, Korea Teacher:

Slides:



Advertisements
Similar presentations
EYYUP ORAK Material requirements planning (MRP) is a computer-based inventory management system designed to assist production managers in.
Advertisements

Project Management Process. Project Complexity means that: a team of people are needed to supply expertise the work needs to be broken into manageable.
New Product and Service Development Children’s Cloth Company.
Project quality management Cody Ronning 3/23/2015.
Seminar Pemasaran Seminar Pemasaran Konsep Marketing.
Fundamentals of Information Systems, Second Edition
System Engineering Instructor: Dr. Jerry Gao. System Engineering Jerry Gao, Ph.D. Jan System Engineering Hierarchy - System Modeling - Information.
GREENING SUPPLY CHAIN IN RETAIL SECTOR
© The McGraw-Hill Companies, Software Project Management 4th Edition Managing contracts Chapter 10.
Copyright © 2005 Pearson Education Inc. Personal Selling and Direct Marketing Chapter 17 PowerPoint slides Express version Instructor name Course name.
MAREKTING OF SERVICES Features..
SDLC Phase 2: Selection Dania Bilal IS 582 Spring 2009.
( Chapter 2 ) ( 3rd semester )
Release & Deployment ITIL Version 3
QUALITY MANAGEMENT SYSTEM ACCORDING TO ISO
KEEPING LABOR AND OVERHEAD COSTS DOWN Controlling Labor and Overhead Costs as a Long Term Strategy.
Atif Iqbal, R. K. Bagga.  Appropriate mechanism for good governance with the involvement of Information Technology in the system of the government and.
Change Management “Getting from where you are, to where you want to be”
MSF Requirements Envisioning Phase Planning Phase.
Rational Unified Process Fundamentals Module 4: Disciplines II.
Chapter 13: Developing and Implementing Effective Accounting Information Systems
ISO 9000 & TOTAL QUALITY ISO 9000 refers to a group of quality assurance standards established by the International Organization for Standardization.This.
Marketing Strategy and the Marketing Plan
Marketing Management Online marketing
© EAGLE Registrations Inc CONFIDENTIAL 1 Experience Speaks of Lessons Learned ASQ Illiana February 15, 2011.
Configuration Management (CM)
MD Digital Government Summit, June 26, Maryland Project Management Oversight & System Development Life Cycle (SDLC) Robert Krauss MD Digital Government.
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
Project Life Cycle.
Systems Analysis and Design
Introduction to Making Multimedia
Notes of Rational Related cyt. 2 Outline 3 Capturing business requirements using use cases Practical principles  Find the right boundaries for your.
PLANNING ENGINEERING AND PROJECT MANAGEMENT By Lec. Junaid Arshad 1 Lecture#03 DEPARTMENT OF ENGINEERING MANAGEMENT.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
PRJ566 Project Planning & Management Software Architecture.
Chapter 6: THE EIGHT STEP PROCESS FOCUS: This chapter provides a description of the application of customer-driven project management.
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.
Creativity and the Business Idea
RUP Deployment RUP Deployment Workflow
Technology Commercialization Technology Commercialization, 2011 Sanjay Dhole, Technology Programs Coordinator Maricopa SBDC.
Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts.
The common structure and ISO 9001:2015 additions
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
1 TCS – Internal Use ILP Training Material New Product Development (NPD) Process.
© 2013 Gartner, Inc. and/or its affiliates. All rights reserved. Gartner is a registered trademark of Gartner, Inc. or its affiliates. The Value Review.
David M. Kroenke and David J. Auer Database Processing Fundamentals, Design, and Implementation Appendix B: Getting Started in Systems Analysis and Design.
CHANGE READINESS ASSESSMENT Measuring stakeholder engagement and attitude to change.
10-1 McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved.
Ass. Prof. Dr. Özgür KÖKALAN İstanbul Sabahattin Zaim University.
1 MARKETING AND MARKETING MANAGEMENT Module 1. 2 Objectives Defining marketing and marketing management The scope of marketing Some fundamental marketing.
Contract management 1. Acquiring software from external supplier This could be: a bespoke system - created specially for the customer off-the-shelf -
MANAGEMENT INFORMATION SYSTEM
Information Technology Planning
Process 4 Hours.
Personal Selling and Direct Marketing
EE Third-Party Solicitation Process Workshop Solicitation Alignment
Fundamentals of Information Systems, Sixth Edition
External Validation of Quality Programs
Personal Selling and Direct Marketing
Chapter 5 :The Business Plan (Creating and Starting The) Venture
Software Documentation
Personal Selling and Direct Marketing
QUALITY MANAGEMENT SYSTEM
Order-to-Cash (Project-Based Services) Scenario Overview
Software life cycle models
Introducing Requirements Change Management Process into ISO/IEC 12207
Nada Al Dosary Edited By: Maysoon AlDuwais
ISO 9000 Dr. S. Thomas Foster, Jr..
Order-to-Cash (Project-Based Services) Scenario Overview
External Validation of Quality Programs
Presentation transcript:

Development of integrated design methodology for various types of product- service systems Author: Tuan A. Tran and Joon Y. Park – DGU, Korea Teacher: Soe-Tsyr Daphne Yuan Presenter: Wei Xiaochen

Outline Introduction Literature review Proposed methodology Illustrating examples Conclusion

Introduction

Product service systems (PSSs) were classified into types Product oriented PSS Use oriented PSS Result oriented PSS The benefits of PSS to consumer, provider, environment and society are result from the higher level of satisfaction, increased competitiveness, decreased environmental impact and material savings. The main benefit of PSS for the company is that it pushes for continuous business improvement, quality improvement, and better company-customer relationship.

Introduction(Cont.) The main challenges in adopting PSS: Consumer may not be enthusiastic about ownerless consumption The manufacturer may be concerned with pricing, absorbing risks and shifting organization PSS design and development itself is a challenge.

Literature review

Some methodologies are case-specific, and others are suitable for designing of a broad range of PSSs. Major limitations of existing PSS design methodologies : The differences in PSS design processes for different types of PSS (Product/Use/Result oriented) are not discussed. The roles and responsibilities of the stakeholders in co-designing PSS offerings are not clearly defined. The importance of the co-creation among stakeholders is only mentioned in insufficient detail. Integrating products and services is discussed as a major objective. The overall processes involved in this integration are well detailed, but the intricate steps within each stage are not mentioned.

Literature review(Cont.) This paper aims to develop a PSS design methodology which works for all types of PSSs provides guidelines to designers in designing PSS for implementation, considers the consumer co – creation, approaches the design of PSS from systemic level, meaning that the PSS design process takes into account all PSS elements: products, services, stakeholders, business models and organizational structure, covers the whole PSS lifecycle.

Proposed methodology

Product is available. Service can be considered as an ”additional value.” The most “general” type of PSS The service deliver to the customer is essential. The product can be considered as a “mean” to realize the service.

Proposed methodology(Cont.) Depending on the portions of product and service Product component Service component Service component Product component

Proposed methodology(Cont.) Check the validity of PSS ideas. Check the feasibility of PSS planning Check the consistency of product, service, and other elements: business model, organizational structure

Proposed methodology(Cont.) Check the compatibility of product, service, and other PSS elements: business model, organizational structure

PSS Idea Development Proposed methodology(Cont.) Design Activities Opportunity Scanning Business Model PSS Type PSS Idea Stakeholder Involvement User: Idea Generation, Idea Evaluation Others: Idea Generation, Idea Evaluation Checkpoint G1 Validity of PSS ideas.

PSS Planning Proposed methodology(Cont.) Design Activities Resource Allocation Team Formation Market Segmentation PSS Scheduling Stakeholder Involvement User: PSS Portfolio Evaluation Supplier: Technology Availability (support systems) Checkpoint G2 Feasibility of PSS plan

Requirement Analysis Proposed methodology(Cont.) Design Activities Needs Identification Needs Analysis Benchmarking PSS Specifications Stakeholder Involvement User: Requirement input, Specification Evaluation Others: Specification Evaluation Checkpoint G31, G32, G33 Consistency of product, service and other PSS elements

Design and Integration Proposed methodology(Cont.) Design Activities Concept Design Detail Design. PSS Integration Stakeholder Involvement All Stakeholders: Concept Evaluation Checkpoint G41, G42, G43 Compatibility of product, service and other PSS elements

Test and Refinement Proposed methodology(Cont.) Design Activities Test implementation Feedback & Refinement Stakeholder Involvement User: Test & Feedback Checkpoint PSS is ready to deliver

Implementation Proposed methodology(Cont.) Design Activities PSS Delivery Use Support Stakeholder Involvement User: Utilization & Feed back Checkpoint

Retirement & Recycling Proposed methodology(Cont.) Design Activities PSS Retirement Disposal/ Recycling Stakeholder Involvement User: Disposal Suppliers: Disposal Plan Checkpoint End of life

Illustrating examples

Illustrating examples----Product-oriented PSS Company A: Traditional: the customer purchases a document from the website, he receives a hyperlink to download the file from the company’s repository Limitations: There is no guarantee that the files will not be shared to the public or among non-buyers illegally when providing support services to customers via the website, the company has no way to know if the support requester is the one who truly purchased the product

Illustrating examples----Product-oriented PSS(Cont.) A new business model combines product and services The company sells each PDF file with one uniquely embedded tracking code. This tracking code will be used as the support code (with a limited number of support tickets). When customers ask for support from the company, they would need to declare their own support code. A support ticket has been completely used. Support history of the customer will be updated and the number of remaining tickets will be subtracted.

Illustrating examples----Product-oriented PSS(Cont.) Opportunity Scanning: Market need and the company’s capability Business Model: Product (PDF file) + Service (support) PSS Type: Product oriented PSS (Product + additional services) PSS Idea: Selling product with higher service level than traditional sales. User involvement: Idea Generation, Idea Evaluation

Illustrating examples----Product-oriented PSS(Cont.) Resources Allocation: All capabilities are available at hand Team Formation: Marketing + Documentation production and delivery + Customer support personnel Market Segmentation: Students, Self-learners PSS Scheduling: Set the time frame to design the PSS, time to launch, assign tasks.

Illustrating examples----Product-oriented PSS(Cont.) Needs Identification: Collect the needs of customers Needs Analysis: Translate the needs into the team’s language Benchmarking: Compare with existing solutions and products PSS Specifications: Set up specifications: length, amount of support tickets, support timing, etc. User involvement: User – Requirement input.

Illustrating examples----Product-oriented PSS(Cont.) Product Component Concept & Detailed Design: Develop the concept & detailed design of product, i.e. the document. The product is available. Service Component Concept & Detailed Design: Design the service accordingly, i.e. fix the final specification. PSS Integration: Set up delivery channel User involvement: Concept Evaluation

Illustrating examples----Product-oriented PSS(Cont.) Test implementation: Release test version to uses Feedback & Refinement: Get feedback and refine User involvement: Test and Feedback PSS Delivery: Deliver PSS Use: Customers use the PSS Support User involvement: Continuing Feedback PSS Retirement: End of PSS Disposal/Recycling: Electronic document, no recycling

Illustrating examples----Use-oriented and result-oriented PSS The sanitary of IDEO.ORG Background: Kumasi, Ghana lacks sanitary services, and most of the citizens in the area cannot afford a toilet at home and the public toilets have serious problems in terms of cleanness and convenience. A new business model: providing the citizens with toilets, waste cartridges (as products) together with the service of collecting waste cartridges, replacing new cartridges, and disposing of the waste.

Illustrating examples----Use-oriented and result-oriented PSS(Cont.)

Opportunity Scanning: There is a need for sanitary service with low cost Business Model: Provide toilet and waste collecting service with fee PSS Type: Use oriented PSS with high portion of service PSS Idea: Provide service and collect payment monthly Outsider involvement: Ideas from the internet community.

Illustrating examples----Use-oriented and result-oriented PSS(Cont.) Resources Allocation: Design and production are available Team Formation: A team consists of designers, engineers, writers and local workers. Market Segmentation: people who live in the compound in Kumasi PSS Scheduling: Set the time frame to design the PSS, time to launch, assign tasks.

Illustrating examples----Use-oriented and result-oriented PSS(Cont.) Needs Identification: Interview customers + visit the site to assess Needs Analysis: Translate the needs into the team’s language PSS Specifications: Set up specifications: service type, period of collecting waste, type and size of toilet, etc. User involvement: User – Requirement input

Illustrating examples----Use-oriented and result-oriented PSS(Cont.) Service Component Concept & Detailed Design: Develop the concept & detailed design of service, i.e. what type of service to provide to the local citizens, how frequent of collecting waste, how much to charge monthly, etc. Product Component Concept & Detailed Design: Design the product ac-cording to the service conditions. PSS Integration: Set up delivery channel

Illustrating examples----Use-oriented and result-oriented PSS(Cont.) Test implementation: Release test versions to local citizens Feedback & Refinement: Get feedback and refine User involvement: Test and Feedback PSS Delivery: Deliver the package; Set up and train the local team. Use: Customers use the PSS User involvement: Continuing Feedback PSS Retirement: End of contract, if any Disposal: Dispose of the old device and replace with a new one.

Illustrating examples (Cont.) With the methodology proposed in this paper, PSS designers can follow design steps to design and develop PSS from the start with PSS idea to the final PSS offering as the output of the process.

Conclusions

The proposed PSS design is generic so that it can work with various types of PSSs, practical enough to guide designers. The proposed methodology also takes into account user involvement, business model and organizational structure in designing PSSs. The proposed design process is still at conceptual level. For future work, the research plan to detail the design process with more insights to make the design process more practical for designers. It will also include more case studies to clarify the design methodology and compare the methodology to previous works.

Thank you!