Advanced Aspects of IT-Infrastructures in Healthcare · Information Technology but not the associated people, Processes and documentation. Advanced Aspects of IT-Infrastructure in

Betrieb von IT-Infrastruktur (1)Operations

VorlesungWS 2012 – 22.11.2012

Advanced Aspects of IT-Infrastructures in Healthcar e

Dipl.-Ing. Herbert Rulitz

WS 2012 – 22.11.2012

INSO - Industrial SoftwareInstitut für Rechnergestützte Automation | Fakultät für Informatik | Technische Universität Wien


Weitere Termine:

� 22.11.2012 - Betrieb von IT-Infrastruktur, 1. Teil

� 29.11.2012 - ITIL

� 13.12.2012 - Betrieb von IT -Infrastruktur, 2. Teil

Advanced Aspects of IT-Infrastructure in Healthcare 2012

� 13.12.2012 - Betrieb von IT -Infrastruktur, 2. Teil

� 20.12.2012 - Ausschreibung von IT-Infrastruktur, Fal lbeispiel

� 10.01.2013 - Neues Krankenhaus Nord als Fallbeispiel , aktuellerUmsetzungsstand

� 24.01.2013 - Prüfung

Content

Operations Overview2

Operations Areas3

Example: Operational Disaster4

Definition 1

Advanced Aspects of IT-Infrastructure in Healthcare 2012 3

Q & A6

Example: Lessons Learned5

Content


Operations Areas3


Definition 1


Q & A6


IT Service Management Lifecycle

� IT Infrastructure Library (ITIL) is the most widely accepted approach to IT Service Sanagement. It provides a best-practice framework for identifying, planning, delivering and supporting IT services to the business.


ITIL V3 Components

5

Definition of Service Operation

� IT InfrastructureAll of the hardware, software, networks, facilities, etc., that are required to Develop, Test, deliver, Monitor, Control or support IT Services. The term IT Infrastructure includes all of the Information Technology but not the associated people, Processes and documentation.


� Service OperationService Operation is the phase in the IT Service Management Lifecycle that is responsible for ‘business-as-usual’ activities.

Service Operation is where the value is actually delivered.

Source: ITIL V3

6

Main Goals of Service Operation

� achieving effectiveness and efficiency in the delivery and support of services

� ensure value for the customer and the service provider

� maintain stability in Service Operations, therefore allowing for changes in design, scale, scope and service levels

� providing methods and tools for use in the two major control


� providing methods and tools for use in the two major control perspectives:� reactive� proactive

� providing knowledge to make better decisions in areas such as managing the availability of services, controlling demand, optimizing capacity utilization, scheduling of operations and fixing problems

7

Content


Operations Areas3


Definition 1


Q & A6


Development Lifecycle

Operations - Overview


Does this also apply to the IT Operations …?

9

Operations - Overview

Operations area divided into:

� Organizational Aspects� Management Commitment� IT Strategy breakdown to Service Strategy� Personnel / Human resources

� Communication� To the customer

Organization


� To service providers� Internal communication� Reporting

� IT Operation� Operations architecture� service level agreements (SLAs)� operating level agreements (OLAs)

10

IT OperationCommunication

Importance of Service Operation

� The way in which an organization’s IT infrastructure and its supporting IT Service Management processes are ope rated will have the most direct and immediate short-term beari ng upon service quality.


service quality.

� Service Operation is extremely important, as it is on a day-to-day operational basis that events occur which can adver sely impact service quality.

11

Target: High Availability

� Comparison of the availability as a percentage per year and the resulting effective downtime


Content


Operations Areas3


Definition 1


Q & A6


Organizational Aspects I

Management Commitment

� enabling IT to meet the business objectives� Embedding in organization hierarchy� Integration in overall Organization Strategy

� honoring the business value� Operation of services shows the actual value


� Operation of services shows the actual value� Funding strategy in operation phase

� transparent communication to customers and clients � Taking responsibility� Backing up operational concerns

14

Organizational Aspects II

IT Strategy breakdown to Service Strategy

� Balance of internal IT view versus external busine ss view� IT as a set of IT services (the external business view)

� Focus on experience by its users and customers.� Focuses on what needs to be done and when and less on how this should be

achieved

� IT as a set of technology components (internal IT view).


� IT as a set of technology components (internal IT view).� Focus on achieving good performance and availability of ‘its’ systems� Focus on how to manage the technology, less on how its performance relates to

IT services

� Solving conflict between maintaining the status quo and adapting to changes in the business and technological environme nts

15

Organizational Aspects III

Personnel / Human resources

� Sourcing Strategy

� Recourses planning� Day-by-day business vs. peak situations

� Training of operation personnel� Technology Training� Service oriented training plan


� Service oriented training plan� Training on new or customized processes and service designs� Competence training in dealing with and managing client relationship and

interaction

� Knowledge building - and keeping!� Avoiding knowledge drain

16

Communication I

Communication

� Internal communication� Routine operational communication� Communication between shifts� Communication in projects� Communication related to changes� Communication related to exceptions� Communication related to emergencies


� Communication related to emergencies� Communication of strategy and design to Service Operation teams.

� To the customer

� To service providers

17

Communication II

� Reporting � Performance reporting� Service Level Management reporting� Service Operation team or department performance (internal only)

� Guidelines� Communication Plan – Who?� Communication Policy – When?


� Communication Policy – When?� Definition of Medium – How?

� Prerequisite� Plan and path well defined for every process� Transporting clear messages� Avoiding complex or cumbersome policies� Avoiding ‘Information-flooding’

18

IT Operation

IT Operation

� Operations architecture� Systems management

� Hardware – Software – Security� Monitoring and control

� Performance monitoring� System/Network monitoring� Recurring activities


� Recurring activities

� Event management� Exception handling

� Service Level Agreements (SLAs)� Contract between customer and service provider

� Operating Level Agreements (OLAs)� Definition of internal structures for delivering SLAs

19

Systems Management I

� Hardware management� Hardware inventories� Hardware maintenance� Vendor management

� Service contracts� Firmware updates

� Storage management


� Storage management � Capacity monitoring� Capacity planning� Archive solutions

� Production scheduling - coordination� Installations� Deployments� Maintenance

20

Systems Management II

� Software management� Software inventory and installation� Packaging and distribution� Anti-virus and anti-malware management

� Security management� Access control (physical, electronically)� User's activities monitoring


� User's activities monitoring� Anti-manipulation measures� Maintaining legal standards

21

Monitoring and control

� Availability, performance and capacity monitoring� Of Systems, Server, Network, Storage, Services …� Logging status changes and performance counters

� Alert/Status Notifications� eMail, SMS, application/scripts

� Automated reporting

� Necessary for Service Level Agreements (SLAs)


� Necessary for Service Level Agreements (SLAs)

� Controlling recurring activities� Backup� Archiving� Update management (software, configuration, …)� Hardware replacements (coordination with Change Management)

22

Systems Operation Center (SOC) I

� Specialization depending on organization size an focus� Helpdesk/Servicedesk (Support)� System Administration� Network Operation� Security Operation

� Main functions� Operation – Maintenance – Fault Management

Possible focuses


� Possible focuses� Support - Operating - Monitoring - Management

� Provided service levels:� 24hours x 7days vs. 8hours x 5days

� Sourcing strategy� InHouse - OutSourced

23

Systems Operation Center (SOC) II

� Basic Role distribution (selection)� 1st level Operations Agent

� Monitoring, incident management, � Support-helpdesk� Triggering and controlling recurring tasks

� 2nd Operations Supervisor / Team Leader� Complex problems and anomalies� Only reachable through the 1st Level


� Only reachable through the 1st Level � Not involved in helpdesk services� Configuration and capacity management� Experienced in administration and configuration of used technologies

� 3rd Operations Expert� Operations planning and supervising� Providing Management reporting� High level of experience and deep knowledge of the used technologies� Knowledge transfer between 2nd and 3rd Level Support important

24

Systems Operation Center (SOC) III

� Role distribution and exclusion (sample)


Content


Operations Areas3


Definition 1


Q & A6


Example: Operational Disaster

� Project� Upgrade of a business critical software application in the intensive care

department

� Customer - Regional Hospital� 20 departments� 1000 beds� 50.000 patients per year treated in-house� 2000 employees


� 2000 employees� IT-Department

� 15P total: 5 technical, 10 administrational (HIS/SAP)

� Vendor� Countrywide eHealth software distributor� Exclusive national distributor of the software package provided by a global

eHealth company� Nationwide 5 comparable installations

27


� General Contractor (GC)� European multi Tier IT Company� Specialized Departments for eHealth IT� Application Service Provider� Project Management at Large� Distributor an operator of own Health Information System

� Several installations Europewide


� Project SetUp� GC provides different Services to Customer� Some Services are provided by sub-contractors� Sub-contructor for Intensive Care Software is the mentioned Vendor� Vendor has additional independent contracts/services with Customer

28


� General Contractor (GC)� European multi Tier IT Company� Specialized Departments for eHealth IT� Application Service Provider� Project Management at Large� Distributor an operator of own Health Information System

� Several installations Europewide


� Project SetUp� GC provides different Services to Customer� Some Services are provided by sub-contractors� Sub-contructor for Intensive Care Software is the mentioned Vendor� Vendor has additional independent contracts/services with Customer

29


� System Architecture� Servers outsourced to general contractor� Network connection managed by GC� Administration of virtualized Servers by GC� Administration of OS, Application and Database by Vendor� Local stations administered by Hospital IT� Local network managed by external Vendor

� Disaster begins 1 month after Upgrade


� Disaster begins 1 month after Upgrade� Application crashes� Bad performance� Loosing confidence in the overall System� Additional work for Hospital personnel� Data loss (suspicion)

� One week full downtime of application� Switching to paper administration

30

Content


Operations Areas3


Definition 1


Q & A6


Example: Lessons Learned

� Looking for someone to blame weakens solution find ing� “Who is guilty?” … only legal relevance

� No single root cause� Technology – Planning - Communication

� Disaster is result of combination� Technology changes� Insufficient monitoring� No overall Change Management


� No overall Change Management � No overall Configuration Management� Missing communication/escalation plans� Missing interaction between vendor and general contractor

� Solution� Active management an proactive operation

“If you failed to plan – you planned to fail”

32

Content


Operations Areas3


Definition 1


Q & A6


Thank you!

� Question? & Answers!



Weitere Termine:

� 29.11.2012 - ITIL

� 13.12.2012 - Betrieb von IT-Infrastruktur, 2. Teil

� 20.12.2012 - Ausschreibung von IT -Infrastruktur, Fallbeispiel


� 20.12.2012 - Ausschreibung von IT -Infrastruktur, Fallbeispiel

� 10.01.2013 - Neues Krankenhaus Nord als Fallbeispiel , aktuellerUmsetzungsstand

� 24.01.2013 - Prüfung

Documents

Advanced Aspects of IT-Infrastructures in Healthcare · Information Technology but not the associated people, Processes and documentation. Advanced Aspects of IT-Infrastructure in