David Chen IMS, University Bordeaux, France Service Modelling Language and Potentials for a New Standard Workshop IWEI 2013 – Enschede, Netherlands March 26, 2013

Introduction Research work carried out under the frame of FP7 MSEE Integrated Project MSEE: Transition from product based manufacturing company to product-related service virtual enterprise Service (system) modelling to support service engineering and implementation Approach: use of Enterprise Modelling techniques and Model Driven

Service Model Driven Engineering Architecture Human related modelling Machine related modelling IT related modelling Business Service Modelling Technology Independent Modelling Technology Dependent Modelling Services in virtual enterprises (software, process, human, material handling devices (machine, robots), etc…) Implementation (software coding, select human and machine components from the market)

Modelling language constituents

Business Service Modelling ResourceFunctionality Stakeholder Decision Performance indicator ProductValue provide measured byrelated to have control relate to have concern apply Customer consume Partner contribute have Organization Decision structure linked to apply ServiceProcess have apply

Business Service Modelling ResourceFunctionality Stakeholder Decision Performance indicator ProductValue provide measured byrelated to have control relate to have concern apply Customer consume Partner contribute have Organization Decision structure linked to apply ServiceProcess have apply Actigram (IDEF0)USDL concepts GRAI grid and netsECOGRAIPOP* product IDEF3, BPMN EN/ISO ARIS modelling language DITF Smart Network model Organization chart IEM language

Template ‘Process’

Business Service Modelling – IIustration example provide measured byrelated to have control relate to linked to has concerns apply uses has Service Electrical car battery maintenance Process PR1=On line service booking and payment process Customer Electric car buyers Product Electric Car Battery Value -Improve 'image of car manufacturer -Increase confidence of customer to buy electrical car Decision structure To be defined Decision D1=Scheduling decision; D2=Supplying decision; D3=Resource allocation decision Performance Indicator PI1=Service rate (number of services provided on time/total number of services requested) Functionality F1=cleaning; F2=Recharging; F3=Reparing Resource R1=Technician; R2=Charger Organization Decentralized networked organization Partners -Feu Vert -Speedy -Others Stakeholder -Car manufacturer -Battery providers -Project sponsor (bank)

Service Template Header Example Construct label['Service']Serive Identifier[Identifier of the service instance]S001 Name[name of the service instance]Electric car battery maintenance Design authority*[ / of the person/organisation with authority to design/maintain this particular instance] Body DOMAIN[Domain of the service]Maintenance (after sale) DESCRIPTION[short textual description of the functionality / utility] This service is to cleaning, recharging, repairing (replacing parts) of electric car battery OBJECTIVE[Short textual description]keep battery function at its 90% capacity during 3 months after a maintenance CONSTRAINT[Short textual description]Need 24 hours delay to deliver service, must booking the service from Web NATURE['Physical' or 'Information' or 'human']Human and physical CLASSIFICATION[Refer to Product Service System (PSS) classification] Additional Service

Technology Independant Modelling Resource providecomposed of have Organization is a HardwareMachineHumanSoftware Data run on used by is a Organization unit responsible to ServiceProcess used by

Technology Independant Modelling Resource providecomposed of have Organization is a HardwareMachineHumanSoftware Data run on used by is a Organization unit responsible to ServiceProcess used by IT related part Machine related part Human related part

Technology Independant Modelling Resource provide composed of have Organization is a HardwareMachineHumanSoftware Data run on used by is a Organization unit responsible to ServiceProcess -EN/ISO EN/ISO UML USDL concepts BPMN IDEF1 IDEF1x E/R Responsibility matrix WSDL REST used by

Technology Dependant Modelling Resource providecomposed of have Organization is a HardwareMachineHumanSoftware Data run on used by is a Organization unit responsible to ServiceProcess used by IT related part Machine related part Human related part Layout implemented in

Technology Dependant Modelling Resource provide composed of have Organization is a HardwareMachineHumanSoftware Data run on used by is a Organization unit responsible to ServiceProcess -EN/ISO Smart Network EN/ISO UML BPEL Internal Schema Physical Schema WSDL REST Layout implemented in USDL ServLab

Potentials for Standardisation Adopt MDSEA as a standard service modelling architecture under which modelling language can be developed Develop metamodel of service modelling constructs at the three modelling levels under MDSEA, focus on BSM level? Map service modelling constructs to existing relevant enterprise modelling techniques Relevant standardization working groups in enterprise modelling standardisation (CEN TC310/WG1 and ISO TC184 SC5/WG1).