strutture:lnf:dr:calcolo:services:portfolio
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
strutture:lnf:dr:calcolo:services:portfolio [2018/02/22 15:08] – [Table] dmaselli@infn.it | strutture:lnf:dr:calcolo:services:portfolio [2018/02/22 15:09] (current) – [Service Portfolio] dmaselli@infn.it | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Service Portfolio ====== | ||
+ | **Service Portfolio**: | ||
+ | |||
+ | ---- | ||
+ | |||
+ | **Service**: | ||
+ | |||
+ | **Service component**: | ||
+ | |||
+ | ---- | ||
+ | |||
+ | **NOTE**: A service is usually composed of several service components. | ||
+ | |||
+ | **NOTE**: Although a service component underlies one or more services, it usually does not create value for a customer alone and is therefore not a service by itself. | ||
+ | |||
+ | [[http:// | ||
+ | |||
+ | ---- | ||
+ | |||
+ | |||
+ | ^ Service | ||
+ | | E-Mail | ||
+ | | AFS (home+project) | ||
+ | | Login Interattivo Linux | LNF | Live | oVirt, NFS, AFS | ||
+ | | VPN | LNF + INFN | Live | Radius, Internet | ||
+ | | Network-plugs | ||
+ | | Network-WiFi | ||
+ | | *print.lnf.infn.it | ||
+ | | www, | ||
+ | | www, | ||
+ | | agenda.infn.it | ||
+ | | wiki.infn.it | ||
+ | | ... | | ||
+ | |||
+ | |||
+ | ---- | ||
+ | |||
+ | ===== REQUIREMENTS ===== | ||
+ | |||
+ | * PR1.1 A service portfolio shall be maintained. All services shall be specified as part of the service portfolio. | ||
+ | * PR1.2 Design and transition of new or changed services shall be planned. | ||
+ | * PR1.3 Plans for the design and transition of new or changed services shall consider timescales, responsibilities, | ||
+ | * PR1.4 The organisational structure supporting the delivery of services shall be identified, | ||
+ | including a potential federation structure as well as contact points for all parties involved. | ||
+ | |||
+ | ===== OBJECTIVE ===== | ||
+ | To define and maintain a service portfolio | ||
+ | |||
+ | === ACTIVITIES: INITIAL PROCESS SETUP === | ||
+ | * Define a way to document the service portfolio. | ||
+ | * Define a way to describe / specify a specific service. | ||
+ | * Set up an initial service portfolio (including service specifications) covering at least all live services provided to customers, as far as they are in the scope of the service management system. | ||
+ | * Create a map of the bodies / parties (organisations, | ||
+ | * Identify and describe the broad role of each party in service provisioning. | ||
+ | * Identify a single contact point for each body / party. | ||
+ | |||
+ | === PROCESS INPUTS === | ||
+ | * Customer demand and requirements | ||
+ | * Understanding of the service provider’s resources and capabilities | ||
+ | * Understanding of the service provider’s limitations and constraints | ||
+ | |||
+ | === ACTIVITIES: ONGOING PROCESS EXECUTION === | ||
+ | * Manage and maintain the service portfolio | ||
+ | * Add a service to the service portfolio | ||
+ | * Update a service in the service portfolio | ||
+ | * Retire a service in the service portfolio | ||
+ | * Manage the design and transition of new or changed services | ||
+ | * Create and approve a service design and transition package | ||
+ | * Update a service design and transition package | ||
+ | * Manage the organisational structure involved in delivering services | ||
+ | |||
+ | === PROCESS OUTPUTS === | ||
+ | * A complete and up-to-date service portfolio | ||
+ | * Valid and consistent service descriptions / specifications | ||
+ | * Service design and transition packages for new or changed services |
strutture/lnf/dr/calcolo/services/portfolio.txt · Last modified: 2018/02/22 15:09 by dmaselli@infn.it