Difference between revisions of "SSE Meeting 34"

From Service Systems Engineering Group Wiki
Jump to: navigation, search
(Created page with "== Attendees == John Davies, Iain Cardow, Sarwar Ahmad, Andrew Farncombe, Neil Hunter. == Overview == *Why go for a Service solution? ** What are the benefits for the Suppli...")
 
 
(6 intermediate revisions by one user not shown)
Line 1: Line 1:
 
== Attendees ==
 
== Attendees ==
  
John Davies, Iain Cardow, Sarwar Ahmad, Andrew Farncombe, Neil Hunter.
+
John Davies, Iain Cardow, Simon Wright, Andrew Farncombe, Neil Hunter.
  
== Overview ==
+
== ASEC 2018 feedback ==
*Why go for a Service solution?
+
SW did a great job as the only core team member at the event.
** What are the benefits for the Supplier and the Customer?
+
* Paper on use of AI techniques to production of System Specification went well.
* Why you will (/or will not) win a Service Contract?
+
* Paper on Service Centric Analysis was not presented but is in the Proceedings.
*What is the big picture for buying and selling Services?
+
* Workshop on use of Stakeholder Diagram attended by six people but went well.
** Can these be used to understand the processes for developing, providing, and using services?
+
*What types of service contract are there?
+
**What are the cost models for the different types of contract?
+
  
== Why go for a Service solution? ==
+
* Poster displayed but not a major attraction 
What are the benefits for the Supplier and the Customer?
+
  
=== For the Supplier: ===
+
It was felt that the focus of ASEC was on MBSE applied in different situations
  
*Use of existing environment
+
== SEE workshop at ASEC ==
*Use of existing service components
+
 
 +
*- Based on stakeholders in the NHS
 +
*- Revealing differences to a Systems-based approach.
 +
NHS stakeholder onion diagram
 +
* Service providers doctors, nurses, para medics
 +
* Service support: managers
 +
* Service beneficiary: Patients
 +
 
 +
== MBSE presentations ==
 +
 
 +
* Some feeling that what is covered by MBSE can be covered in other ways.
 +
* MBSE is a general grouping of methods within hich there are several methodologies: UML, SysML, NAF, DoDAF, MoDAF,... and support tools.
 +
 
 +
* MBSE has been used for electrical/electronic systems or high level business systems.
 +
* does not include all information and can’t put non-functional requirements in MBSE in a useful manner
 +
* Problem space is bigger than the tool box available.
 +
 
 +
== Presentation on use of SE in pharmaceutical domain ==
 +
 
 +
* Getting product out of the door
 +
* biotechnical area
 +
* Cancer  analysis
 +
* Designer drugs
 +
* Gene sequencing
 +
* 'SE is common sense'
 +
 
 +
== Aerospace group ==
 +
Feeling that MBSE is not sufficient
 +
* Process, Methods, Tools being worked on for humans using competency framework
 +
* Some large and small businesses have dropped the use of Systems Engineering as it has not added value.
 +
 
 +
== Discussion on use of MBSE ==
 +
 
 +
It was felt that the work of the Service Systems Engineering Group would be more acceptable for presentation at ASEC if it used MBSE diagramming techniques (such as SysML).  This may overcome the perceived barrier in getting papers accepted at ASEC. (It is accepted that papers could be submitted to the International Conference but this is too costly and )
 +
 +
The work presented in the last two papers could be reworked using MBSE. This should also test
 +
* If MBSE is suitable for this work
 +
* If MBSE can cover the concepts and techniques identified for SSE
 +
* If modifications are needed
 +
* If text-based documentation is better used in some areas
 +
* If use of MBSE reveals issues within our current view of SSE
 +
 
 +
As the SSE core team does not have an MBSE expert with access to an advanced support tool, it was agree to contact members of the MBSE working group with a view to doing a joint exercise.
 +
 +
== Service Development and Lifecycle ==
 +
Following on from 'bubble diagram' of for buying and selling services presented at the last meeting, these items have been organised into Lifecycle covering
 +
 
 +
Service Supplier
 +
* Develop Business Strategy
 +
 
 +
* Develop Business Opportunity
 +
* Deliver Services
 +
* Develop Future Business
 +
 
 +
Service Customer
 +
* Develop Technical Services Policy
 +
* Develop Business Requirement/Needs
 +
* Use Services
 +
* Develop Future Requirement/Needs
 +
 
 +
This overlaps with previous work on definitions and lifecycles - need to revisit those to check if/how output fit together and rationalise if necessary.
 +
 
 +
 
 +
== Actions ==
 +
 
 +
* Simon Wright to contact MSE working group members with regard to using MBSE to re-write papers.
 +
 
 +
* John Davies to rationalise/sort out various lifecycle work.
 +
 
 +
== Date of Next Meeting ==
 +
 
 +
29 April, Rolls Royce, Fiton, 10:30 - 14:30

Latest revision as of 10:01, 21 February 2019

Contents

[edit] Attendees

John Davies, Iain Cardow, Simon Wright, Andrew Farncombe, Neil Hunter.

[edit] ASEC 2018 feedback

SW did a great job as the only core team member at the event.

  • Paper on use of AI techniques to production of System Specification went well.
  • Paper on Service Centric Analysis was not presented but is in the Proceedings.
  • Workshop on use of Stakeholder Diagram attended by six people but went well.
  • Poster displayed but not a major attraction

It was felt that the focus of ASEC was on MBSE applied in different situations

[edit] SEE workshop at ASEC

  • - Based on stakeholders in the NHS
  • - Revealing differences to a Systems-based approach.

NHS stakeholder onion diagram

  • Service providers doctors, nurses, para medics
  • Service support: managers
  • Service beneficiary: Patients

[edit] MBSE presentations

  • Some feeling that what is covered by MBSE can be covered in other ways.
  • MBSE is a general grouping of methods within hich there are several methodologies: UML, SysML, NAF, DoDAF, MoDAF,... and support tools.
  • MBSE has been used for electrical/electronic systems or high level business systems.
  • does not include all information and can’t put non-functional requirements in MBSE in a useful manner
  • Problem space is bigger than the tool box available.

[edit] Presentation on use of SE in pharmaceutical domain

  • Getting product out of the door
  • biotechnical area
  • Cancer analysis
  • Designer drugs
  • Gene sequencing
  • 'SE is common sense'

[edit] Aerospace group

Feeling that MBSE is not sufficient

  • Process, Methods, Tools being worked on for humans using competency framework
  • Some large and small businesses have dropped the use of Systems Engineering as it has not added value.

[edit] Discussion on use of MBSE

It was felt that the work of the Service Systems Engineering Group would be more acceptable for presentation at ASEC if it used MBSE diagramming techniques (such as SysML). This may overcome the perceived barrier in getting papers accepted at ASEC. (It is accepted that papers could be submitted to the International Conference but this is too costly and )

The work presented in the last two papers could be reworked using MBSE. This should also test

  • If MBSE is suitable for this work
  • If MBSE can cover the concepts and techniques identified for SSE
  • If modifications are needed
  • If text-based documentation is better used in some areas
  • If use of MBSE reveals issues within our current view of SSE

As the SSE core team does not have an MBSE expert with access to an advanced support tool, it was agree to contact members of the MBSE working group with a view to doing a joint exercise.

[edit] Service Development and Lifecycle

Following on from 'bubble diagram' of for buying and selling services presented at the last meeting, these items have been organised into Lifecycle covering

Service Supplier

  • Develop Business Strategy
  • Develop Business Opportunity
  • Deliver Services
  • Develop Future Business

Service Customer

  • Develop Technical Services Policy
  • Develop Business Requirement/Needs
  • Use Services
  • Develop Future Requirement/Needs

This overlaps with previous work on definitions and lifecycles - need to revisit those to check if/how output fit together and rationalise if necessary.


[edit] Actions

  • Simon Wright to contact MSE working group members with regard to using MBSE to re-write papers.
  • John Davies to rationalise/sort out various lifecycle work.

[edit] Date of Next Meeting

29 April, Rolls Royce, Fiton, 10:30 - 14:30

Service Systems Engineering Group Wiki

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox