1 / 42

Multi-layer ICT Management

Multi-layer ICT Management. Presented by Andy Park. Introduction. There is no one RIGHT way to manage ICT. There is no WRONG way to manage ICT. The ideas presented here are personal. They have taken shape over many years. ICT management is often erratic. ICT management can be organized.

kaitlin-dennis
Télécharger la présentation

Multi-layer ICT 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. Multi-layer ICT Management Presented by Andy Park

  2. Introduction • There is no one RIGHT way to manage ICT. • There is no WRONG way to manage ICT. • The ideas presented here are personal. • They have taken shape over many years. • ICT management is often erratic. • ICT management can be organized. Andy Park

  3. How do you think it should be done? • Hierarchy? • Divisions? • Departments? • Groups? Andy Park

  4. Whichever way you look at it: • Identify “blocks”. • Set up communication between “blocks”. Andy Park

  5. Have you considered layers but with good communication? • Divide ICT management into layers. • Good communication is essential. Andy Park

  6. Firstly • Each layer involves HW, SW and people. • And the layers are: Andy Park

  7. 1) The user layer • The (end) customer. • Everything needed to look after the customer. Andy Park

  8. 1a) The customer could be: • A group of users. • A department. • A company. • Company relations (EDI). • Developers. • The outside world (via internet etc.). BISL “Focus” Andy Park

  9. 1b) Looking after the customer • User management. • Customer relations. • Security. • Helpdesk. • Maybe even sales, marketing of ICT services. Andy Park

  10. 2) The application layer • Everything the users directly interacts with. Andy Park

  11. 2a) The application layer • Office tools. • Printing, plotting, scanning. • General applications. • ERP/MRP/CRM. • Development tools and compilers. • ICT support tools. • Factory/Laboratory automation software. Andy Park

  12. 2b) The application layer • Functional application management • Functional specification • Technical application management • Software development • Software management (SW C&D) ASL “Focus” Andy Park

  13. 3) The data layer • Data is what the applications process. Andy Park

  14. 3a) The data layer • Database management. • File and disk management. • Tape management / backups. • HSM, RAID, SAN, NAS. • File shares. • Middleware (data access) products. Andy Park

  15. 4) The system layer • The basic environment to run the applications. Andy Park

  16. 4a) The system layer • Clients (Terminals, PC’s, Tablets, Smartphones, Virtual Desktops, ATM’s). • Servers, CPU, Memory. • Operating systems. • Special peripherals. Andy Park

  17. 5) The infrastructure layer • Everything to connect the pieces. • Network. • Environment. Andy Park

  18. 5a) The network • Network management. • Cables, switches, routers, hubs, bridges. • Firewalls. • TCP/IP, SNA, DECnet, OSI. • Telephone. • WWW. Andy Park

  19. 5b) The environment • Electricity, gas, water. (Coffee?) • Cooling, heating. • Rooms. • Fire prevention. Andy Park

  20. To summarize • The user layer. • The application layer. • The data layer. • The system layer. • The infrastructure layer. • But this is not the end of the story! Andy Park

  21. Major advantages • Good foundation for costing. • € per m2, per CPU unit, per GB, per application • The right experts working together. • Experts doing their own job. Andy Park

  22. Major disadvantages • Requires trust that each layers does its job. Andy Park

  23. (Management) Communication • The layers are not independent. • Without some sort of communication nothing happens. • You need to recognize and understand the processes involved. • Each process covers ALL the layers. Andy Park

  24. ITIL • Information Technology Infrastructure Library. • A set of concepts on which to design your own ICT management processes. Andy Park

  25. ITIL groups • The service support group. • daily work. • The service delivery group. • vision for the future. Andy Park

  26. Service support • The processes involved with the day to day running of ICT. Andy Park

  27. Service support • Configuration management. • Incident management. • Problem management. • Change management. • Software control and distribution. Andy Park

  28. Configuration management • What are our assets (HW, SW and People)? • What are the relations between assets? • What needs registering? • Keeping information up to date. Andy Park

  29. Incident management • Identifying incidents (by tools). • Identifying incidents (from customers). • Helpdesk - contact with customer. • Keeping track of who is “solving” incident. • When is an incident a problem? Andy Park

  30. Problem management • Working out what is the real problem. • Finding solutions. • Defining “Known errors”. • Generating “request for change”. Andy Park

  31. Change management • Processing Request for change. • Planning. • Is it worth doing? • What are the consequences? • What are the priorities? Andy Park

  32. Software control and distribution • Keeping track of SW versions. • Who needs which version? • Who has which version? • How to get new versions where they are needed. Andy Park

  33. Service delivery • The processes involved with the long term. • Where are we going? • What are our goals? Andy Park

  34. Service delivery • Service level management. • Customer liaison. • Cost management. • Capacity management. • Availability management. • Contingency planning. Andy Park

  35. Service level management • Analysis and evaluation of services. • Creation of “service catalog”. • Creation of “Service Level Agreements”. • SLA is the result of discussions between customers and ICT. • Setting up reporting. Andy Park

  36. Customer liaison • General discussion with customer at high level. • Future plans. • What’s going wrong. Andy Park

  37. Cost management • Identify what everything is really costing. • Calculation of what (new) things will really cost. (not just purchase price). • Possibility of invoicing customers. Andy Park

  38. Capacity management • How are resources being used? • Identification of when expansion will be required. • What will a new service need? Andy Park

  39. Availability management • When are services required? • When can we do maintenance? • How reliable do things need to be? • What are the consequences if something's not available? • Security issues. Andy Park

  40. Contingency planning • What can go wrong? • Should we allow for it? • What are we going to do about it? • Everything from just making a backup to having hot standby external computer sites. Andy Park

  41. Map ITIL on management layers I T I L The User Layer (BISL) The Application Layer (ASL) The Data Layer The System Layer The Infrastructure Layer Andy Park

  42. Summary • Now you know what you are managing and how. • What = the ICT management layers. • How = the ICT processes. • Do you have the knowledge, tools, and people to “get organized”? Andy Park

More Related