1 / 18

Configuration Management

Configuration Management. Block 13. Overview. Intent Be able to meet the responsibilities of EA for configuration management in Defence Content Introduce ITIL Determine risks of configuration changes Report risks. Why should EA bother about Configuration Management?.

hlouise
Télécharger la présentation

Configuration Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Configuration Management Block 13

  2. Overview Intent Be able to meet the responsibilities of EA for configuration management in Defence Content • Introduce ITIL • Determine risks of configuration changes • Report risks

  3. Why should EA bother about Configuration Management? • How many of you have been involved in Configuration or Change Management? • Why? • Can you give one reason why Configuration/ Change Management is important to EA?

  4. Welcome to ITIL • Who knows ITIL? • The Information Technology Infrastructure Library (ITIL) • set of (6) books describing good practice • produced by UK Office of Government Commerce • supported by IT Service Management Forum (ITSMF) • covered by BS15000 now (temp) ISO 20000 and AS 8018 Service management Parts 1 and 2 • has accreditation process … and increasing demand

  5. ITIL Service Support • We are most interested in ITIL Service Support • Have a look at Chapter 7 “Configuration Management” • And Chapter 8 “Change Management”

  6. Other Standards concerned with Configuration • ISO 20000 is not the only standard that mentions ICT Configuration Management • What else does? • ISO 12207: 1997 Information Technology -Software life cycle processes

  7. Configuration Management and Change Management Configuration Management = model of ICT in play(“As-is” Architecture) Change management= amending configuration because of problem or incident+ enhancing configuration to take up opportunity(amending Architecture short of full “To-be” analysis?)

  8. Change Management Process Basically • Receive request • Log request, compare with others • Determine initial impact • Gain approval from Change Advisory Board (incl business managers) • Consider risks of change and priority of effort • Incl impact upon EA (we hope) • Schedule changes • Make changes, test, and retest • Log effects

  9. Technology Regulatory Framework • In DefenceChange Management will be governed by the “Technical Regulatory Framework”

  10. Activity: Use of EMS • Use the Group Decision Support System (GDSS) or Electronic Meeting System (EMS) to discuss roles and responsibilities for configuration/ change management

  11. Use of AnnL in Change management • AnnL can be used to assess the risks of requested changes

  12. Systems Dependency “The hip bone is connected to the thigh bone …” • Some things are not important in themselves but they enable other things to happens • So, they “inherit” the importance of those other things What examples of dependency are there

  13. Reporting risks

  14. To Whom are Risks Reported? Under the Technical Regulatory Framework • Who analyses the risks? • What is the ‘house style for the risk report? • Who approves the changes?

  15. Yet another use of AnnL

  16. Activity: AnnL in Project Management • In teams • For 15 minutes • Go to the Task sections of the In sheet for the Case Study • Have a fiddle with some items • See what happens

  17. Change management as Projects • When does a change request become a project?

  18. Summary There is a pretty good process in place for managing changes to ‘configurations’ (EAs). It is all about managing the risks of proposed changes - even if it is not said that way. Next Block • Compliance and Audit will be considered in Block 17 • But next is …

More Related