Workshop on Service Systems Engineering at ASEC 2016

Purpose

To provide INCOSE members with a view of the Working Group.
To provide the Working Group with feed-back on work done and ideas for the way forward.

Julian Johnston, Michael Emes, Tim James, John Davies

Definitions are useful in clarifying what is being talked about by different people involved with services and in moving ahead with this work.
When comparing Services with Systems (Products)the User has more involvement with Services
Services are more alive than products, they can be changed rapidly
Service evolve, whereas systems have occasional updates
Properties of a Service as 'ilities' are more important for services such as railways.
Finding four or five groupings of services would be very useful, the issue is to find what axes are important in gropng them.
- On demand or continuously available or periodic (eg car, taxi, bus)
- Frequency of use = everyday or occasional (commuter train vs intercity)
- Depth of involvement of the user
- Responsiveness to individual users
- Triggered vs On-going
- Bespoke or off the shelf (ala carte or fast food)

Focus on Healthcare and Transport - these are the areas that will draw most interest and have most exploitation
Properties/ilities are important but may have different meanings/applications for services
Interest in Service Architecture for Healthcare - covered briefly in IS2016 paper
Want a way of grouping services that are similar - but need to look at 'axes' and contract types rather than engineering.