David ChenIMS, University Bordeaux, France
Service Modelling Language and Potentials for a New Standard
Workshop IWEI 2013 – Enschede, NetherlandsMarch 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
Machinerelated
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
DecisionPerformanceindicatorProductValue
provide
measured byrelated tohave
control
relate to
have concern
apply
Customer
consume
Partnercontribute
haveOrganization
Decisionstructurelinked
to
applyService Process
have
apply
Business Service Modelling
ResourceFunctionality
Stakeholder
DecisionPerformanceindicatorProductValue
provide
measured byrelated tohave
control
relate to
have concern
apply
Customer
consume
Partnercontribute
haveOrganization
Decisionstructurelinked
to
applyService Process
have
apply
Actigram (IDEF0) USDL concepts
GRAI grid and netsECOGRAIPOP* product
IDEF3, BPMN
EN/ISO 19440ARIS modelling languageDITF Smart Network model
Organization chart
IEM language
Template ‘Process’
Header Construct label [‘Process’] Identifier [Identifier of the process instance] Name [name of the process instance] Body Objective [Short description of the process objectives] Trigger [Condition this process instance is triggered] Result [Output of this process instance] Constraint [Constraint that may apply on this process instance] Sub-process [List of sub-process] [Graphical representation]
Example: IDEF3 Process diagram Relationships to other model elements SERVICE [Identifier/name of service concerned by the process: described by Service template]
RESOURCE [Identifier/name of resource used by the process: described by Resource template] Other Relationships RELATED TO MODEL LEVEL [Refer to BOM, TIM, TSM modelling level] : BOM REALTED TO SLM PHASE [Refer to service lifecycle phases] : Requirement
Business Service Modelling – IIustration example
provide
measured byrelated tohavecontrol
relateto
linkedto
has concerns
applyapply
apply
uses
has
ServiceElectrical car battery maintenance
ProcessPR1=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
DecisionD1=Scheduling decision; D2=Supplying decision; D3=Resource allocation decision
Performance IndicatorPI1=Service rate (number of services provided on time/total number of services requested)
FunctionalityF1=cleaning; F2=Recharging; F3=Reparing
Resource
R1=Technician; R2=Charger
OrganizationDecentralized networked organization
Partners-Feu Vert-Speedy-Others
Stakeholder-Car manufacturer-Battery providers-Project sponsor (bank)
Service Template
Header ExampleConstruct label ['Service'] SeriveIdentifier [Identifier of the service instance] S001Name [name of the service instance] Electric car battery maintenanceDesign authority* [<identifier> / <name> 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 physicalCLASSIFICATION [Refer to Product Service System (PSS)
classification]Additional Service
Technology Independant Modelling
Resource
provide composed of
haveOrganization
is a
Hardware Machine HumanSoftware
Data
run on
used by
is a is a
Organization unit
responsible to
Service Process
used by
Technology Independant Modelling
Resource
provide composed of
haveOrganization
is a
Hardware Machine HumanSoftware
Data
run on
used by
is a is a
Organization unit
responsible to
Service Process
used by
IT related part
Machine related part
Human related part
Technology Independant Modelling
Resource
provide composed of
haveOrganization
is a
Hardware Machine HumanSoftware
Data
run on
used by
is a is a
Organization unit
responsible to
Service Process
-EN/ISO19440
EN/ISO19440
UML
USDLconcepts
BPMN
IDEF1IDEF1xE/R
Responsibility matrixWSDL
RESTused by
Technology Dependant Modelling
Resource
provide composed of
haveOrganization
is a
Hardware Machine HumanSoftware
Data
run on
used by
is a is a
Organization unit
responsible to
Service Process
used by
IT related part
Machine related part
Human related part
Layout
implemented in
Technology Dependant Modelling
Resource
provide composed of
haveOrganization
is a
Hardware Machine HumanSoftware
Data
run on
used by
is a is a
Organization unit
responsible to
Service Process
-EN/ISO19440-SmartNetwork
EN/ISO19440
UML
BPEL
InternalSchemaPhysical Schema
WSDLREST
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).
Top Related