Beruflich Dokumente
Kultur Dokumente
SYSTEMS MANAGEMENT
Dr. Anindita Paul
Indian Institute of Management Kozhikode
INFRASTRUCTURES
Session 6
Learning Objective
What are the different components of MIS infrastructure?
What are the primary types of MIS Infrastructure?
What are the three primary areas associated with MIS Infrastructure?
What are the environmental impacts of MIS?
What are the three components of a sustainable MIS Infrastructure
and its business benefits?
What are the characteristics of an Agile MIS Infrastructure?
Hardware
Software
Network
Client
Server
Supporting change
Agile MIS Infrastructure
The services a firm is capable of providing to its customers, suppliers, and employees are a direct function of its IT
infrastructure. Ideally, this infrastructure should support the firms business and information systems strategy. New
information technologies have a powerful impact on business and IT strategies, as well as the services that can be
provided to customers.
Supporting change
Agile MIS Infrastructure
Failover
specific type of fault tolerance, occurs when a redundant storage server
offers an exact replica of the real-time data and if the primary server
crashes the users are automatically directed to the secondary server or
backup server. High speed and expensive
Failback
the primary machine recovers and resumes operations taking over from
the secondary server.
Grid Computing
Virtualization
Virtualization is the
abstraction of IT resources that masks the physical nature and boundaries of those
resources from users.
a form of consolidation that can benefit sustainable MIS infrastructures in a variety of ways,
for example:
Virtualized Computing
Cloud Computing
Cloud computing model in which any and all IT resources are
delivered as a set of services via the Internet
PaaS
Accessibility
Availability
Maintainability
Portability
Reliability
Scalability
Usability
Accessibility
Accessibility - Refers to the varying levels that define what a
user can access, view, or perform when operating a system
Web accessibility Allows people with disabilities to use the
Web
Administrator access Unrestricted access to the entire
system
Availability
Availability Time frames when the system is operational
Unavailable Time frames when a system is not operating
and cannot be used
High availability System is continuously operational at all
times
Maintainability
Maintainability How quickly a system can transform to
support environmental changes
Organizations must watch todays business, as well as
tomorrows, when designing and building systems
Systems must be flexible enough to meet all types of
business changes
Portability
Portability The ability of an application to operate on
different devices or software platforms
Reliability
Reliability - Ensures a system is functioning correctly and
providing accurate information
Reliability is another term for accuracy when discussing the
correctness of systems within the context of efficiency IT
metrics
Vulnerability a system weakness that can be exploited by
a threat
Scalability
Scalability - How well a system can scale up, or adapt to the
increased demands of growth
Performance - Measures how quickly a system performs a
process or transaction
Capacity planning - Determines future environmental
infrastructure requirements to ensure high-quality system
performance.
How does Web 2.0 drive capacity planning?
Usability
Usability The degree to which a system is easy to learn
and efficient and satisfying to use
Serviceability How quickly a third-party can change a
system to ensure it meets user needs and the terms of any
contracts, including agreed levels of reliability,
maintainability, or availability
CareGroup
CareGroup was formed in a three way merger of hospital in 1996.
The merger was precipitated by
increased need for negotiating and contracting power to respond to the HMOs.
He simultaneously completed an
Engineering course and a Medical
course at Berkeley Engineering
School and UCSF Medical School
respectively
Turn of events
When John took over, the possibility of problems arising
from the turn of the century was on the front burner.
A backup system was developed in attempt to mitigate
possible damages resulting from the event.
By 2002, the issue of decentralization of the systems of the
hospitals had been address through the creations of a
common system for all hospital.
Centralised
Shared customer
(patients)
Shared data (patient
medical records, test
results etc)
Centralized system
Linked Processes
Decentralised
Operations will not be able to compromise and continued should one particular
networks goes down
After effects
Monopolised the services of a centrally located network switch. No other data could
get through this switch, nor was it able to respond to queries from other network
components asking if it was still functioning.
Since the network was physically redundant throughout, there were alternative paths
along which the data could flow.
As network components tried to calculate new paths along which data could flow,
they started deciding which would act as primary and which as backups and
became confused.
Algorithms could no longer operate correctly resulting in chaos (backup components
acting as primary hence duplicating primarys functionality, messages started
bouncing back and forth in an endless loop etc.)
Lessons Learnt
Do not hesitate to bring in the experts to make sure your network is configured properly
Do not let any one individual in your IT group become the sole point of failure
IT staff relied too heavily on single employee as theres no one to offer a second opinion
about the networks configuration
Ensure that staff is kept up to date with the skill sets required to handle the systems
after going through the upgrades
Everyone would experiment with the local network in one way or another, always not the
changes and be vigilant over it
Lessons Learnt
Institute rigorous network change control
Adapt to externalities
There are limits to customer-centric responsiveness
Have backup procedures in which you can have confidence