Available online at ScienceDirect. Procedia CIRP 16 (2014 )

Transcription

1 Available online at ScienceDirect Procedia CIRP 16 (2014 ) Product Services s and Value Creation. Proceedings of the 6th CIRP Conference on Industrial Product-Service s Interfaces of IPS²-Execution s Connecting Virtual Organization Units for the Delivery Management of IPS² Thomas Dorka*, Friedrich Morlock, Horst Meier Ruhr-University of Bochum, Chair for Production s, Universitätsstr. 150, Bochum, Germany * Corresponding author. Tel.: ; fax: address: dorka@lps.rub.de Abstract For the management of the delivery of Industrial Product-Service s (IPS²), an IPS²-Execution (IPS²-ES) can be used. This software system provides means of managing the provider network as well as planning the IPS² delivery. However, to execute these tasks, different types of data are required and have to be collected from the different partners involved in the lifecycle of IPS². This paper describes which data types are needed to efficiently and effectively organize the IPS² delivery. Additionally, the origin of each data type is shown and a way of connecting network partners as virtual organization units to the IPS²-ES is described. Conclusively, an outlook for further research is given Elsevier B.V. This is an open access article under the CC BY-NC-ND license 2014 The Authors. Published by Elsevier B.V. ( Selection and peer-review under responsibility of the International Scientific Committee of The 6th CIRP Conference on Industrial Product- Selection and peer-review under responsibility of the International Scientific Committee of The 6th CIRP Conference on Industrial Service s in the person of the Conference Chair Professor Hoda ElMaraghy. Product-Service s in the person of the Conference Chair Professor Hoda ElMaraghy Keywords: Industrial Product-Service s (IPS²); IPS²-Execution (IPS²-ES); Service Delivery Management 1. Introduction Providing customer-specific value in an industrial setting can be achieved by Industrial Product-Service s (IPS², [1 4]). They allow for an integrated use of product and service shares while uniting suppliers, partners and customers to achieve superior solutions. However, the knowledge-intensive socio-technical nature of IPS² ([2]) also constitutes a major challenge for providers throughout the whole lifecycle. Thus, particularly for IPS², their development, planning and delivery are non-trivial tasks. An IPS² provider needs partners who have expertise in different fields to be able to deliver a contracted customer value. Therefore, a network of partners is formed to support the IPS² provider in the execution of these activities [5]. The network consists of several virtual organization units (VOU), each representing the parts of a company that are involved in the partner network and can be perceived as an individual organization. This paper shows what data need to be exchanged between the VOU to be able to efficiently organize the delivery of multiple IPS² with the aid of a software system. During the development phase, a partner network is defined and a model [6, 7] for each IPS² provided by the supplier is created. The models contain detailed descriptions of the product and service shares of a specific IPS². Both the information about the network and parts of the model data can then be used to organize the IPS² delivery during the operation phase. They are especially needed for the functionality that is provided by an IPS²-Execution (IPS²-ES, [8 10]). An IPS²-ES is a software system that supports the IPS² provider in the organization of the IPS² delivery and the management of the partner network. Therefore, it needs information about the delivery processes that have to be scheduled and the resources that are needed to execute the processes. For each IPS², information about the delivery processes can be found in the model. However, the information about the available resources is not directly at hand. Hence, basic information about the network partners is Elsevier B.V. This is an open access article under the CC BY-NC-ND license ( Selection and peer-review under responsibility of the International Scientific Committee of The 6th CIRP Conference on Industrial Product-Service s in the person of the Conference Chair Professor Hoda ElMaraghy doi: /j.procir

2 374 Thomas Dorka et al. / Procedia CIRP 16 ( 2014 ) needed so that their software systems can be connected to the IPS²-ES. By doing so, they can deliver the required data about the resources they supply and can receive updated delivery schedules from the IPS²-ES. The structure of this paper is as follows: Chapter 2 provides a short introduction about the state of the art and related works. By giving detailed information in chapter 3 and 4 about what data is submitted, who is the sender and who is the receiver, what the contents of that data are and what fundamental interfaces have to be established, this paper conclusively shows how the IPS²-ES can efficiently support the organization of the delivery of IPS². The conclusion is summarized in chapter State of the Art This chapter defines the foundation on which the presented findings are based. Therefore, apart from a general definition of IPS², the delivery in networks as well as the planning for IPS² and IPS²-Execution s are described Industrial Product-Service s (IPS²) According to [2] IPS² can be defined as follows: An Industrial Product-Service is characterized by the integrated and mutually determined planning, development, provision and use of product and service shares including its immanent software components in Business-to- Business applications and represents a knowledge-intensive socio-technical system The main aim of IPS² is to deliver customer value instead of supplying products and offering services. By doing so, the IPS² provider stays in contact with the IPS² customer throughout the whole lifecycle of the IPS², which consists of the following phases [11]: planning, development, implementation, operation (also delivery and use) and closure. The focus of the presented research lies on the operation phase, where a network of partners around the IPS² provider and the customer work together to deliver the IPS² IPS² Delivery in s After planning, developing and implementing an IPS², the delivery and use of the IPS² is the purpose of the operation phase. As an IPS² provider does not necessarily have all required know-how and capacity to deliver all IPS², a network of partners is formed to support the IPS² provider. This value creation network ([12]), as mentioned in [13] and further developed in [5], consists of product suppliers, service suppliers, IPS² module suppliers, the IPS² provider and the IPS² customers. For the delivery, a delivery plan is created with a specific planning algorithm so that the existing demand for delivery processes can be distributed to the available resources provided by the network Planning for IPS² For the delivery of IPS², strategic, tactical and operational planning is used. Literature provides only few approaches for planning in the context of IPS². In [14] capacity planning is the main focus. The dissertation presents a good overview of planning approaches for products as well as for services and also develops an integrated approach for IPS². In [15] and its related works [16 19], a method for strategic capacity planning and operational resource planning is proposed. According to [20], it can be argued that the planning horizon for the strategic capacity planning is practically a tactical planning approach in comparison with other planning literature. Nevertheless, the planning method, which leverages a genetic algorithm, can be used to create a delivery plan that can serve as the basis for the IPS² delivery. For software systems supporting the IPS² delivery, the task of planning is one of the main functions they have to provide 2.4. IPS²-Execution (IPS²-ES) In [10], a definition of an IPS²-ES is given as follows: An IPS²-Execution is the essential software system for the IPS² operation phase that supports the IPS² provider in the provision of customer value by adaptive IPS² delivery planning, IPS² network management and an integrated performance measurement method. The adaptive IPS² delivery planning refers to the planning methods described in chapter 2.3, while the IPS² network management integrates the partners of the provider network (described in chapter 2.2) into the IPS²-ES. Not least, the integrated performance measurement method (see [21]) helps to ensure an efficient and effective organization of the IPS² delivery as an integrated service in an IPS²-ES. To execute the tasks listed in the definition and provide necessary information, data from different parties are required, which is described in the following chapter. 3. Exchange with an IPS²-ES Not only does an IPS²-ES require special data for the execution of its tasks, but it also provides other essential data. There are seven types of data that have to be considered to support the delivery of IPS² with an IPS²-ES (see Table 1): provider network data, IPS² model data, resource profile and availability data, service communication data, delivery plan data, unplanned demand data and delivery process feedback data. The different types of data have to be supplied in due time by the participants of the provider network. During the use of an IPS²-ES, data about the provider network is first needed. This data defines which partners are involved in the provider network and hence the IPS²-ES can enable the data exchange with these partners VOU inside the IPS²-ES. Also, services provided by these partners (e.g. the online ordering of spare parts) can be made available. The IPS²-ES uses a self-configuration mechanism to achieve both actions without the need of user intervention [9]. The provider network data also defines which types of resources (i.e. human resources, tools or spare parts) or which specific resources a partner may contribute to the delivery of IPS².

3 Thomas Dorka et al. / Procedia CIRP 16 ( 2014 ) Type Provider IPS² Model Resource Profile and Availability Service Communication Delivery Plan Unplanned Demand Delivery Process Feedback Table 1. Types and their Sections Sections 1. Partner configuration 1.1 Enabled Partner IDs Enabled Resource IDs / Types Enabled Service IDs 2. IPS² 2.1 IPS² ID 2.2 IPS² Location 3. Delivery Processes 3.1 Delivery Process ID 3.2 Time Windows / Schedule for Execution 3.3 Requirements of Resources Required Remote Human Resources Required Human Resources Required Tools Required Spare Parts 3.4 Replacement Delivery Process IDs 4. Resources (Human Resources, Tools, Spare Parts) 4.1 Resource Availability 4.2 Resource Costs 4.3 Resource Profile 4.3 a Human Resource Skills 4.3 b Tool Types 4.3 c Spare Part Type 5. IPS² 5.1 IPS² Availability for Service 6. Service Communication This data depends on the interfaces needed or provided by each specific service. 7. Delivery Plan (possibly filtered) 7.1 Validity Period 7.2 Delivery Processes Assigned Time Window Assigned Resources (Human Resources, Tools, Spare Parts) 7.3 Planned Transportations Assigned Resources (Human Resources, Tools, Spare Parts) Origin/Destination Mode of Transportation 7.4 Planned Overnight Stays Assigned Human Resources Location 8. Unplanned Delivery Process Request 8.1 Requesting IPS² ID 8.2 Requested Delivery Process ID 8.3 Requested Time Window for Execution 10. Delivery Process Feedback 10.1 Reporting IPS² ID 10.2 Delivery Process ID 10.3 Process Start/End Time/Date 10.4 Number of Errors During Process Execution 10.5 Process Abort (yes / no) Once all partners from the provider network are added and configured, the planning of the IPS² delivery can be prepared. For the planning, the following two types of data are required. First, parts of the general IPS² model data [6] for each IPS², originating from the IPS² development, have to be transmitted to the IPS²-ES. This constitutes the transition from the development phase to the delivery phase inside the IPS² lifecycle. The required information consists of information about the described IPS² (identifier and location) and information about the delivery processes for this IPS². The delivery processes have to be described by a unique identifier (e.g. Micro Milling Spindle Maintenance ), the time windows for execution (e.g. Monday, 8am to Wednesday 7pm ) and the execution schedule (e.g. every two weeks ) and resource requirements (e.g. Spare Part Lubricant xyz, Tool Standard Toolbox and Human Resource Spindle Service Technician ). Examples for Remote Human Resources are service experts that support a service technician through an augmented reality system worn by the technician. A list of delivery processes that can replace this delivery process, if required, can also be added to the description. Secondly, resource profile and availability data is needed for an IPS² delivery planning. This data includes the service availability of an IPS² (also treated as a resource here), i.e. the definition of the time windows the IPS² is available for delivery processes. Apart from that, the resources available for service are specified. For each resource, be it a human resource, a tool or a spare part, its availability, its costs and its profile has to be contained. Here, the resource profile provides a list of the skills of a human resource, the different tool types a tool implements or a definition of the type of a particular spare part. Given the described data, the IPS²-ES can execute the IPS² delivery planning, e.g. as presented in [15]. During the execution of the planning algorithm, route planning services or services for the calculation of logistic costs are contacted. Hence, service communication data, i.e. data that is required to communicate with a given service, is exchanged. However, depending on the services, the communication interfaces might differ between services and therefore, the communication data cannot be described in general. To provide an example, the outgoing service communication data to a route planning service might be an origin and destination pair, while the incoming service data might consist of the duration of travel for the calculated route along with a turnby-turn description of the route. The result of a successful run of the IPS² delivery planning is a delivery plan for all IPS² the IPS² provider supplies. The data about the delivery plan has to be sent out to the partners in the provider network to inform them which of their provided resources is utilized in the newly generated delivery plan. The delivery plan data contains a validity period of the plan and a list of planned delivery processes, planned transportations and planned overnight stays. The scheduled time and the assigned resources are contained for each planned delivery process. The assigned resources, the origin and destination and the mode of transportation (e.g. car, train, taxi, mail, etc.) are specified for each of the planned transportations. Finally, each overnight stay for human resources at specific locations is described. Due to the fact that not all receivers of the IPS² delivery plan are entitled to see all resource assignments, a filtered version of the delivery plan data, containing only

4 376 Thomas Dorka et al. / Procedia CIRP 16 ( 2014 ) information the receiver is authorized to see, may be transmitted. Whenever an unplanned demand for a new delivery process occurs for an IPS², this demand has to be reported to the IPS²-ES in order to schedule the desired process. The data required to issue the request is the identifier of the requesting IPS², the identifier of the requested delivery process and the desired time window for the execution of the process. The newly requested delivery process can then be included in the planning and the newly generated delivery plan data can be sent out. For each delivery process that is executed for an IPS², a process feedback can be reported to the IPS²-ES. This report has to define the reporting IPS² ID, the delivery process ID for which the feedback is given, the start and end time and date of the executed process and the number of errors that occurred during the process execution. Additionally, it can be reported whether the process was aborted, marking the execution of the process as failed. This data is required for the performance measurement method of the IPS²-ES, described in [21], which uses this data to measure the performance of the IPS² delivery. Examples for Key Performance Indicators can be found in [22]. The data types described above show how diverse the different contents are. Moreover, the data do not only differ in their content, but also in their origin (see Figure 1), size and frequency of updates (see Figure 2). In general, the IPS²-ES is connected to other IPS²-specific software systems, namely the IPS²-Lifecycle Management and the IPS²-Control, and to external systems like route planning web services and the heterogonous software landscapes of the network partners. In this software environment, the IPS²-ES receives data required for the organization of IPS² delivery, generates necessary data for the delivery with the use of web services and provides the data to other software systems. It works closely together with the IPS²-Control in a closed feedback loop. Partners Provider and IPS² Model a Resource Profile and Availability Delivery Plan Unplanned Demand and Delivery Process Feedback IPS²-Lifecycle Management IPS²-Control Delivery Plan IPS²-ES Organisation of IPS² Delivery: - Management - Delivery Planning - Performance Measurement Delivery Plan Figure 1. Flows and the IPS²-ES Service Communication External Services (e.g. Route Planning) The provider network data and the IPS² model data both originate from the IPS² development. After the data are created and released, they are stored in the IPS²-Lifecycle Management (IPS²-LMS, [23, 24]) and then sent to the IPS²-ES. Whenever information about the provider network or IPS² model data change inside the IPS²-LMS an update has to be transmitted to the IPS²-ES. Service communication data originates from the IPS²-ES and is sent to one of the external services. The data is used mainly in a request/response type of communication. The IPS²-ES sends out a request to a service to get support in executing its tasks. The contacted service then responds with the requested service data. As mentioned before, the delivery plan data originates from the IPS²-ES. The data is sent to the IPS²-LMS for further reference by parties involved in the IPS² lifecycle. It is also sent out in filtered form to the network partners. The IPS²- Control (IPS²-CS, [25, 26]) needs the delivery plan data to ensure a robust control of the IPS² delivery. Vice versa, the IPS²-CS sends unplanned demand data to the IPS²-ES when the closed loop control for an IPS² is not capable of controlling the IPS² delivery within the boundaries of the given delivery plan. In this case, a new delivery process is necessary and the demand is escalated. Additionally, the IPS²-CS sends feedback data for each delivery process, regardless of whether it has been aborted or successfully finished. The complicated closed loop control represented by the IPS²-ES in conjunction with the IPS²-CS and other support systems is presented more closely in [24]. Not least, resource profile and availability data originate from the partners in the provider network. However, due to the heterogeneous and partner-specific software environments, the data needed by the IPS²-ES is potentially distributed in several software systems in use by the partner. An approach to connect the partners as virtual organization units (VOU) is presented in the next chapter. Size high low low high Frequency of Updates Delivery Plan IPS² Model Resource Profile and Availability Service Communication Provider Delivery Process Feedback Unplanned Demand Figure 2. Size and Frequency of Updates for IPS²-ES Types 4. Connecting Virtual Organization Units for the Delivery Management of IPS² The heterogeneous partners that form the provider network use diverse software systems to store their data. An Enterprise Resource Planning system (ERP, see for example [27]) might store data about product stocks as well as personnel master data, while a Manufacturing Execution (MES, see for example [28]) contains detailed information about the

5 Thomas Dorka et al. / Procedia CIRP 16 ( 2014 ) completion times of new products and a Service Management Software (SMS, see for example [29]) manages personnel availability and assignment data. In another company, the whole setup of software systems is potentially completely different, ranging from simple spread sheets to a highly sophisticated and automated IT environment. However, the IPS²-ES needs to be able to receive data from any given IT setup present at a network partner. As an additional challenge, the data of the partners should be as up-to-date as possible. This is required for the operational planning used in the IPS²- ES, which relies on current data to determine feasible delivery plans (see [21]). To overcome both obstacles for a simple connection of network partners, each network partner is represented in the IPS²-ES as a VOU service (see also [9, 10]). These services hide the partner-specific IT environment and shift the responsibility of up-to-date data to the corresponding network partner. First of all, each partner has to identify where the data the IPS²-ES requires can be found in his software systems. An ideal IPS² supplier has all data already available. However, suppliers without a history of providing resources for the delivery of an IPS² might have to find a way to gather existing data and derive the required information (see [20]). For each software system that contains or can contribute to the required data, an interface needs to be established to transmit data to the corresponding VOU inside the IPS²-ES. Each partner can be represented by more than one VOU in the IPS², if required, allowing for a structured provision of information (e.g. VOU1: Maintenance Service Division, VOU2: Remote Support Service Division). One approach to connect the different software systems of a partner is to build a software-specific adapter for each new software system. For partners who join the provider network at a later point of time, the existing adapters can be reused and extended to fit the new partners needs. By identifying common changes in the adapters, an easily configurable software connector can be developed which can be used with little or no implementation effort. A standard (e.g. XML [30]) or de facto-standard (e.g. JSON [31]) schema should be used for the transmission of the data, e.g. via web services (see [32]). Nevertheless, even proprietary data formats can be used with custom adapter implementations. Having established a way to push the data to the VOU inside the IPS²-ES, it is now in the hand of the supplier to implement the essential task of keeping the data up-to-date. Using this push technology, each part of the resource profile and availability data can be made available in the VOU (see Figure 3). Ultimately, the IPS²-ES can use the data of all VOU using a pull technique because the VOU work like an intermediary storage containing the most recent data of a supplier. 5. Conclusion and Outlook In this paper, data types as well as senders and receivers of data in context of the use of an IPS²-ES have been outlined to foster the profound understanding of an IPS² delivery and the IPS²-ES in particular. The data types and their content as well as the depicted way of connecting VOU with an IPS²-ES can serve as a guideline for future implementations. Additionally, partners wanting to join a provider network for an IPS² delivery can determine what effort they have to invest to provide the required data.. Partner-specific IT Environments Partner 1 Partner N Enterprise Resource Planning Service Management Manufacturing Execution Software s IPS²-ES of Virtual Organization Units Virtual Organization Units 1 1..n. 1. Virtual Organization Units n+1..m n Figure 3. Connecting Partners as Virtual Organization Units in the IPS²-ES In [14, 33] a data model for capacity planning for productservice systems has already been outlined, however, the focus on operational tasks, as implemented by the IPS²-ES, have not been taken into account. Also, approaches for advanced planning and scheduling solutions (see for example [34 36]) have not considered the specific nature of IPS², e.g. the heterogeneous network of VOU. Hence, the findings presented in this paper can serve as valuable input for further research in the area of the delivery of IPS². The active exchange of data between the IPS²-ES and the partners systems as well as IPS²-specific software systems as described in this paper are required to enable the IPS²-ES to efficiently support the IPS² delivery by executing its tasks. As an outlook, prototypical implementations of adapters and case studies with IPS² suppliers can be carried out to enrich the described approach with examples. The findings for the delivery of IPS² with an IPS²-ES can also be used to review the way industrial services are managed today and improve this foundation towards the extensive establishment of IPS². Acknowledgements We express our sincere thanks to the German Research Foundation (Deutsche Forschungsgemeinschaft, DFG) for financing this publication within the Collaborative Research Center Transregio 29 (CRC/TR 29) on Industrial Product- Service s dynamic interdependencies between products and services in the production area.

6 378 Thomas Dorka et al. / Procedia CIRP 16 ( 2014 ) References [1] Sakao T, Lindahl M. Introduction to Product/Service- design. London: Springer-Verlag; [2] Meier H, Roy R, Seliger G. Industrial Product-Service s - IPS². CIRP Annals - Manufacturing Technology 2010;59(2): [3] Aurich JC, Clement MH (eds.). Produkt-Service e: Gestaltung und Realisierung. [Product-Service s: Design and Implementation]. Berlin: Springer; [4] Roy R, Shehab E (eds.). Industrial product-service systems (IPS2): Proceedings of the 1st CIR IPS2 Conference. Bedford: Cranfield University Press; [5] Völker O. Erbringungsorganisation hybrider Leistungsbündel. [IPS² Delivery Organization]. Aachen: Shaker; [6] Bochnig H, Uhlmann E, Nguyễn HN, Stark R. General Model for the IT Support for the Integrated Planning and Development of Industrial Product-Service s. In: Meier H, editor. Product-Service Integration for Sustainable Solutions: Proceedings of the 5th CIRP International Conference on Industrial Product-Service s, Bochum, Germany, March 14th - 15th, Berlin, Heidelberg: Springer; 2013, p [7] Meier H, Dorka T, Morlock F. Hybride Leistungsbündel-Execution (HLB-ES): Plug-In-Framework für eine offene und selbstkonfigurierende Managementsoftware zur HLB-Erbringung. [IPS²- Execution : PlugIn Framework for an Open and Self-Configuring Management Software for IPS² Delivery]. wt Werkstattstechnik online 2013(7/8): [8] Meier H, Dorka T. Robust Manufacturing through Integrated Industrial Services The Delivery Management. In: Windt K, editor. Robust Manufacturing Control. Berlin, Heidelberg: Springer; 2013, p [9] Meier H, Morlock F, Dorka T. Functional Specification for IPS²- Execution s. In: Meier H, editor. Product-Service Integration for Sustainable Solutions: Proceedings of the 5th CIRP International Conference on Industrial Product-Service s, Bochum, Germany, March 14th - 15th, Berlin, Heidelberg: Springer; 2013, p [10] Meier H, Dorka T, Morlock F. Architecture and Conceptual Design for IPS²-Execution s. In: do Carmo Cunha PF, editor. 46th CIRP Conference on Manufacturing s Amsterdam: Elsevier; 2013, p [11] Meier H, Steven M, Funke B, Boßlau M, Keine gen. Schulte J. Complexity and Flexibility of IPS² across various Planning Levels: Functional Thinking for Value Creation. In: Hesselbach J, Herrmann C, editors. Functional Thinking for Value Creation: Proceedings of the 3rd CIRP International Conference on Industrial Product Service s. Berlin, Heidelberg: Springer; 2011, p [12] Hamel G. Leading the revolution. Boston, Mass: Harvard Business School Press; [13] Meier H, Völker O. Service Provision for Industrial Product-Service s. In: Roy R, Shehab E, Hockley Chris, Khan S, editors. Enduring and Cost-Effective Engineering Support Solutions: Cranfield University Press; 2012, p [14] Hübbers M. Modell zur Kapazitätsplanung von Dienstleistungsressourcen in Leistungssystemen. [Model for the Capacity Planning of Service Resources in PSS]. 1st ed. Aachen: Apprimus-Verl; [15] Funke B. Adaptive Planungsmethode zur Terminierung der Erbringungsprozesse hybrider Leistungsbündel. [Adaptive Planning Method for the Scheduling of IPS² Delivery Processes]. Dissertation. Bochum: Shaker; [16] Meier H, Funke B. Resource Planning of Industrial Product-Service s (IPS²) by a Heuristic Resource Planning Approach. In: Sakao T, Larsson T, Lindahl M, editors. Industrial Product-Service s (IPS²): Proceedings of the 2nd CIRP IPS² Conference. Linköping: Linköping University; [17] Meier H, Funke B, Boßlau M. Flexible Resource Planning in the Context of Dynamic IPS² Business Models. In: Hesselbach J, Herrmann C, editors. Functional Thinking for Value Creation: Proceedings of the 3rd CIRP International Conference on Industrial Product Service s. Berlin, Heidelberg: Springer; 2011, p [18] Meier H, Funke B. Planungsmethoden für den Betrieb hybrider Leistungsbündel. [Planning Methods for the delivery of IPS²]. In: Meier H, Uhlmann E, editors. Integrierte Industrielle Sach- und Dienstleistungen: Vermarktung, Entwicklung und Erbringung hybrider Leistungsbündel. [Integrated Industrial Products and Services: Marketing, Development and Delivery of IPS²]. Berlin, Heidelberg: Springer; 2012, p [19] Meier H, Völker O, Krug CM, Funke B. Decentral service delivery by means of flexible organization. In: Industrial Product-Service s: Dynamic interdependency of products and services in the production area. Aachen: Shaker; 2009, p [20] Meier H, Lagemann H, Dorka T. Requirements for transfer and application of IPS² resource planning case-study of a global machine tool manufacturer. In: Shimomura Y, Kimita K, editors. The philosopher's stone for sustainability: Proceedings of the 4th CIRP International Conference on Industrial Product-Service s, Tokyo, Japan, November 8th-9th, Berlin, New York: Springer; 2012, p [21] Meier H, Morlock F, Dorka T. Delivery Management of Industrial Product-Service s Challenges for a Performance Measurement. In: Shehab E, Ball P, Tjahjono B, editors. Proceedings of the 11th International Conference on Manufacturing Research (ICMR2013): Incorporating the 28th National Conference on Manufacturing Research. Cranfield: Cranfield University Press; 2013, p [22] Meier H, Lagemann H, Morlock F, Rathmann C. Key Performance Indicators for Assessing the Planning and Delivery of Industrial Services. 2nd International Through-life Engineering Services Conference. Procedia CIRP 2013;11: [23] Abramovici M, Dang HB, Wolf M. IPS²-KOP: IPS² Knowledge-Based Service-Oriented Lifecycle Management Platform. In: Meier H, editor. Product-Service Integration for Sustainable Solutions: Proceedings of the 5th CIRP International Conference on Industrial Product-Service s, Bochum, Germany, March 14th - 15th, Berlin, Heidelberg: Springer; 2013, p [24] Aurich JC, Schweitzer E, Fuchs C. Life Cycle Management of Industrial Product-Service s. In: Takata S, Umeda Y, editors. Advances in Life Cycle Engineering for Sustainable Manufacturing Businesses. London: Springer; 2007, p [25] Uhlmann E, Raue N. IPS² Control for the Integrated Support of Service Processes. In: Shimomura Y, Kimita K, editors. The philosopher's stone for sustainability: Proceedings of the 4th CIRP International Conference on Industrial Product-Service s, Tokyo, Japan, November 8th-9th, Berlin, New York: Springer; 2012, p [26] Meier H, Uhlmann E, Raue N, Dorka T. Agile Scheduling and Control for Industrial Product-Service s. In: Roberto Teti, editor. Eighth CIRP Conference on Intelligent Computation in Manufacturing Engineering: Elsevier; 2013, p [27] Jacob O (ed.). ERP Value: Springer Berlin Heidelberg; [28] Kletti J. Manufacturing Execution s (MES). Berlin, London: Springer; [29] McNeill W, Maoz M, van Huizen G. Magic Quadrant for Field Service Management; [30] World Wide Web Consortium (W3C). Extensible Markup Language (XML) 1.1 (Second Edition); 2006; Available from: [October 29, 2013]. [31] Crockford D. RFC The application/json Media Type for JavaScript Object Notation (JSON); [32] Schill A, Springer T. Verteilte e: Grundlagen und Basistechnologien. [Distributed s: Principles and Basic Technology]. 2nd ed. Berlin: Springer; [33] Schuh G, Hübbers M, Gudergan G. Structural Model of Resources in Product Service s - A Prerequisite to Portfolio Design and Planning. In: Sakao T, Larsson T, Lindahl M, editors. Industrial Product-Service s (IPS²): Proceedings of the 2nd CIRP IPS² Conference. Linköping: Linköping University; 2010, p [34] Owusu G, Voudouris C, Kern M, Garyfalos A, Anim-Ansah G, Virginas B. On Optimising Resource Planning in BT plc with FOS. In: Chu C, Kacem I, editors. Proceedings of the International Conference on Service s and Service Management, Piscataway, NJ: IEEE; 2006, p [35] Voudouris C, Owusu G, Dorne R, McCormick A. FOS: An Advanced Planning and Scheduling Suite for Service Operations. In: ICSSSM '06. Proceedings of the 2006 International Conference on Service s and Service Management. Piscataway, NJ: IEEE; [36] Dorne R, Voudouris C, Owusu G. An Advanced Planning and Scheduling Platform for Service Enterprise. In: Innovations '07: 4th International Conference on Innovations in Information Technology: conference proceedings, Dubai, November 18-20, Piscataway, N.J.: IEEE; 2008, p