Difference between revisions of "SSE Meeting 24"

From Service Systems Engineering Group Wiki
Jump to: navigation, search
(Created page with "INCOSE UK Service Systems Engineering Working Group Meeting: 27 March 2017, Keynsham, Bristol == Attendees == Andrew Farncombe, Alan Crawford, John Davies, Iain Cardow, S...")
 
(→‎INCOSE IS2017)
 
(6 intermediate revisions by one user not shown)
Line 8: Line 8:
 
Andrew Farncombe, Alan Crawford, John Davies, Iain Cardow, Simon Wright
 
Andrew Farncombe, Alan Crawford, John Davies, Iain Cardow, Simon Wright
  
−
==Review of Health Care Case Studies==
+
==Review of Healthcare Case Studies==
 +
 
 +
===Healthcare sources===
 
Two sources of Case Studies were considered.
 
Two sources of Case Studies were considered.
−
NHS CHAIN - Contact, Help, Advice, Information Network. [[http://www.chain-network.org.uk/chain/index.html]]  
+
* NHS CHAIN - Contact, Help, Advice, Information Network. [[http://www.chain-network.org.uk/chain/index.html]]  
 +
* US Institute of Healthcare.  [[http://www.ihi.org/resources/Pages/CaseStudies/default.aspx]]
 +
 
 +
Both of these contain many Case Studies, but they are about medical or organisational decisions and the effect on patients.  None were found that related to the Health Care Service and how it was provided.
 +
 
 +
===INCOSE IS2017===
 +
Three papers were tagged as Healthcare:
 +
* van der Watt: Healthcare Facility Commissioning – The Transition of Clinical Services
 +
* Uger: Comprehensive Approach to Systems Engineering Capability Development in GE Healthcare.
 +
*Beasley and O'Neil.  Selling Systems Engineering by Searching for the Sweet Spot.
  
−
Iain_C in contact with the Bristol Group with regard to presenting further work and getting feedback.  The Bristol Group are looking at setting up study areas and this could be one of them.
+
Having reviewed these:
 +
* van der Watt describes a new hospital and bringing it into operation.  It uses SoS terminology - so talks about a National Health System rather than a Service.  This paper should be good for comparison of a Systems of Systems view and a Service view.
  
−
=== Competencies for Services ===
+
* Uger: is about Systems Engineering Capability Development not Healthcare.
−
Alan_C presented work taking the existing SE Competencies and asking if Services required a similar, lower, or higher level of competence.  This lead to discussion and some adjustment.  AC will update.
+
  
−
=== Stakeholders ===
+
* Beasley and O'Neil.  Is about Selling Systems Engineering not Healthcare.
−
John D presented a table of Stakeholders concerned with services and relating them to Artefacts of Services and then considering these against the example services we have been considering.  It was felt that these should be linked to process/lifecycle.  The lifecycles in the SE Handbook were considered. It was felt that ITIL and TOGAF were being used extensively for IT services the lifecycles associated with these should be considered.
+
  
−
=== Groups of Services ===
+
== Example Service Representation ==
−
John D had investigated grouping suggested at ASEC but found not major differences to the Characteristics groupings. He had then considered using the Artefacts as a means of grouping, but this had not got very far.   
+
Simon W presented work looking at how to define/represent/model a service to maintain military vehicles. This work has been carried out for an overseas customer over the last year.
 +
===Findings ===
 +
Compared with Systems:
 +
* The same principles, processes and tool used for defining/developing systems are needed for developing systems
 +
* Context diagram is key
 +
* In a layered model, the Service-layer is on top of the Product layer
 +
* The Service life-s=cycle is different
 +
* Stakeholder analysis is needed and is more important for Services than for Systems.
 +
* In contrast to systems, the key stakeholder outside the service.  eg in Healthcare the patient is outside the Service, but in a Systems model the patient could be inside the system.
  
−
== Famework for Service Systems Engineering ==
+
===Way forward ===
−
It was generally felt that current work was missing a framework that would cover/relate major aspects: lifecycle, process, artefacts, stakeholders, lines of development etc. and that providing such a framework would be a major contribution that this group could make.  TOGAF and ITIL provide some of this for IT-based services.  Our work needs to include this as well as the non-IT aspects - Equipment, People, Support, etc.  Agreed that our next meeting will focus on providing this through consideration of an example service.
+
* Simon to send brief analysis/model for comment
 +
* All to study and compare with previous work.
  
 
== Next Meeting ==
 
== Next Meeting ==
  
−
Monday 27 March 2017 11-30 to 15-30, Babcock, Keynsham, Bristol.
+
Monday 5 June 2017 10-30 to 14-30, Rolls-Royce, Filton, Bristol.

Latest revision as of 11:29, 31 March 2017

INCOSE UK Service Systems Engineering Working Group

Meeting: 27 March 2017, Keynsham, Bristol


Contents

[edit] Attendees

Andrew Farncombe, Alan Crawford, John Davies, Iain Cardow, Simon Wright

[edit] Review of Healthcare Case Studies

[edit] Healthcare sources

Two sources of Case Studies were considered.

  • NHS CHAIN - Contact, Help, Advice, Information Network. [[1]]
  • US Institute of Healthcare. [[2]]

Both of these contain many Case Studies, but they are about medical or organisational decisions and the effect on patients. None were found that related to the Health Care Service and how it was provided.

[edit] INCOSE IS2017

Three papers were tagged as Healthcare:

  • van der Watt: Healthcare Facility Commissioning – The Transition of Clinical Services
  • Uger: Comprehensive Approach to Systems Engineering Capability Development in GE Healthcare.
  • Beasley and O'Neil. Selling Systems Engineering by Searching for the Sweet Spot.

Having reviewed these:

  • van der Watt describes a new hospital and bringing it into operation. It uses SoS terminology - so talks about a National Health System rather than a Service. This paper should be good for comparison of a Systems of Systems view and a Service view.
  • Uger: is about Systems Engineering Capability Development not Healthcare.
  • Beasley and O'Neil. Is about Selling Systems Engineering not Healthcare.

[edit] Example Service Representation

Simon W presented work looking at how to define/represent/model a service to maintain military vehicles. This work has been carried out for an overseas customer over the last year.

[edit] Findings

Compared with Systems:

  • The same principles, processes and tool used for defining/developing systems are needed for developing systems
  • Context diagram is key
  • In a layered model, the Service-layer is on top of the Product layer
  • The Service life-s=cycle is different
  • Stakeholder analysis is needed and is more important for Services than for Systems.
  • In contrast to systems, the key stakeholder outside the service. eg in Healthcare the patient is outside the Service, but in a Systems model the patient could be inside the system.

[edit] Way forward

  • Simon to send brief analysis/model for comment
  • All to study and compare with previous work.

[edit] Next Meeting

Monday 5 June 2017 10-30 to 14-30, Rolls-Royce, Filton, Bristol.

Retrieved from ‘http://www.incosewiki.info/Service_Systems_Engineering/index.php?title=SSE_Meeting_24&oldid=217’

Service Systems Engineering Group Wiki

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox