Difference between revisions of "SSE Meeting 33"
From Service Systems Engineering Group Wiki
(→Overview) |
(→Why you will (/or will not) win a Service Contract?) |
||
(3 intermediate revisions by one user not shown) | |||
Line 8: | Line 8: | ||
* Why you will (/or will not) win a Service Contract? | * Why you will (/or will not) win a Service Contract? | ||
*What is the big picture for buying and selling Services? | *What is the big picture for buying and selling Services? | ||
− | |||
** Can these be used to understand the processes for developing, providing, and using services? | ** Can these be used to understand the processes for developing, providing, and using services? | ||
− | |||
*What types of service contract are there? | *What types of service contract are there? | ||
**What are the cost models for the different types of contract? | **What are the cost models for the different types of contract? | ||
− | |||
== Why go for a Service solution? == | == Why go for a Service solution? == | ||
What are the benefits for the Supplier and the Customer? | What are the benefits for the Supplier and the Customer? | ||
− | For the Supplier: | + | |
+ | === For the Supplier: === | ||
+ | |||
*Use of existing environment | *Use of existing environment | ||
*Use of existing service components | *Use of existing service components | ||
Line 35: | Line 34: | ||
*Need to meet SLAs | *Need to meet SLAs | ||
− | Customer | + | === Customer === |
*Lower cost | *Lower cost | ||
*Pay as you go | *Pay as you go | ||
Line 44: | Line 43: | ||
*Service Level Agreement | *Service Level Agreement | ||
+ | === Why you WILL win a Service Contract? === | ||
+ | * Experience of providing services | ||
+ | * Reputation within industry | ||
+ | * Investment to cover extremes of cost model | ||
+ | * Lower cost | ||
+ | * Solution built on standard environment and service components | ||
+ | * Built to integrate with other services | ||
+ | * Good operation | ||
+ | * Good level of support | ||
+ | * Meets SLAs | ||
+ | === Why you will NOT win a Service Contract? === | ||
+ | * Lack of experience | ||
+ | * Lack of reputation | ||
+ | * Price too high | ||
+ | * Not using/familiar with standards: | ||
+ | ** TOGAF | ||
+ | ** ITIL | ||
+ | ** CMMI for services | ||
+ | * Poor level of support | ||
+ | * Not meeting SLAs | ||
+ | |||
+ | |||
+ | == Further Areas to Look at == | ||
− | |||
− | |||
*What is the big picture for buying and selling Services? | *What is the big picture for buying and selling Services? | ||
− | * | + | *What types of service contract are there? |
− | + | *What are the cost models for the different types of contract? | |
− | + | ||
== Start of lifecycle == | == Start of lifecycle == |
Latest revision as of 10:21, 7 January 2019
Contents |
[edit] Attendees
John Davies, Iain Cardow, Sarwar Ahmad, Andrew Farncombe, Neil Hunter.
[edit] Overview
- Why go for a Service solution?
- What are the benefits for the Supplier and the Customer?
- Why you will (/or will not) win a Service Contract?
- What is the big picture for buying and selling Services?
- 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?
[edit] Why go for a Service solution?
What are the benefits for the Supplier and the Customer?
[edit] For the Supplier:
- Use of existing environment
- Use of existing service components
- Less development
- Lower cost of development
- Lower risk of development failure
- Lower management cost
- Lower cost of support
- Lower time to market
- Lower overall risk
- Develop service components for use on other projects
- Can share load of different customers
But
- time until profit
- Needs investment up-front
- Supplier takes more of the risk
- Need to meet SLAs
[edit] Customer
- Lower cost
- Pay as you go
- Upgrades – same functions - do more
- Flexibility- extend and/or change functions
- Integration with other services
- Common look and feel
- Service Level Agreement
[edit] Why you WILL win a Service Contract?
- Experience of providing services
- Reputation within industry
- Investment to cover extremes of cost model
- Lower cost
- Solution built on standard environment and service components
- Built to integrate with other services
- Good operation
- Good level of support
- Meets SLAs
[edit] Why you will NOT win a Service Contract?
- Lack of experience
- Lack of reputation
- Price too high
- Not using/familiar with standards:
- TOGAF
- ITIL
- CMMI for services
- Poor level of support
- Not meeting SLAs
[edit] Further Areas to Look at
- What is the big picture for buying and selling Services?
- What types of service contract are there?
- What are the cost models for the different types of contract?
[edit] Start of lifecycle
Work had been carried out to identify items required to provide and to use services and the links between them. These included
- the Business Strategy
- the Business Success
- the Business System/Service Solution
- the Business Case
- the Business Opportunity
- the Business Offering
- the Potential Customer
- the Potential Market
- the Customer Environment
- the Existing Technical Environment
- the Potential Customer
- the Existing Service Elements
- etc.
[edit] Service Contracts
- Six types of contract, based on Mobile Phones, Car Leasing, were discussed
[edit] Next Meeting
18 February 2019, 10-30 to 14-30, Rolls Royce, Filton, Bristol.