---MIS Assignment # 6---

A cohesive and robust IT infrastructure is of paramount importance for the development of any company. A successful IT department must be able to meet increasing business driven demands, whilst preparing for changing business dynamics in the future.

If I were hired by the university president as an IT consultant, I would you suggest to use or develop such Infrastructures in University. This is to improve not only the system of the University but as well as transactions, internet access and even operations made by the staff.

We define information technology (IT) to include not only computer technology (hardware and software) for processing and storing information, but also communications technology for transmitting information. Advances in computer and communications technologies have enabled firms to pursue IT investments. This will help them to gain maximum advantage from their knowledge assets-to leverage the knowledge of individual employees to the benefit of other employees and the organization as a whole. Businesses have strived to achieve a competitive advantage in the past by competing in one of two ways: 1. By Cost- by being a low-cost producer of a good and service 2. By Differentiation of a product or service- by competing on customer perceptions of product quality and customer support services.

You know, there is not all that much I would actually change about this university. Sure we could use some better facilities and the more diversity the better, but those changes have to take place over time, sometimes a long time. For now I am content with the prospect of throwing out ideas used by other universities to either increase student recruitment or enhance the image surrounding our college, that has without doubt been tarnished in past years.

Infrastructure can be defined as the basic physical and organizational structures needed for the operation of a society or enterprise, or the services and facilities necessary for an economy to function. The term typically refers to the technical structures that support a society, such as roads, water supply, sewers, power grids, telecommunications, and so forth. An underlying base or foundation especially for an organization or system. The basic facilities, services, and installations needed for the functioning of a community or society, such as transportation and communications systems, water and power lines, and public institutions including schools, post offices, and prisons. It s the set of interconnected structural elements that provide the framework for supporting the entire structure.

In other applications, the term infrastructure may refer to information technology, informal and formal channels of communication, software development tools, political and social networks, or beliefs held by members of particular groups. Still underlying these more conceptual uses is the idea that infrastructure provides organizing structure and support for the system or organization it serves, whether it is a city, a nation, a corporation, or a collection of people with common interests.

In the present world, which is dynamic and knowledge based, universities have a much wider role to play in creating, preserving, organizing, transmitting and applying knowledge. Modern educational technologies developed from information technology will certainly change in terms of access, interaction, curriculum and instruction etc. The physical locations and facilities will be less important in defining a college or a university due to the easy on-line access of the educational resources of a higher educational institution to the urban as well as rural public. This will provide opportunities to our high school graduated youths from rural areas as well as urban youths to access higher education without a need to forgo their working and earning opportunities to physically attend a college or a university. So universities need to adopt modern education technologies to provide increase access to knowledge resources.

Online technologies are going to make traditional class room teaching less important in many subjects except where it is absolutely necessary. Therefore interaction between teachers and students will have to play a vital role in imparting higher quality education. This means that more frequent and effective internal mechanism of interaction between university faculty and students need to be developed. This, in turn, causes an external relationship between universities and non-university communities. Such external relationship will necessitate universities to respond quickly to the changes in the outside world. Therefore a mechanism to increase both the internal and external interaction efficiencies has to be developed.

The curriculum and instruction are going to be changed greatly. Because the new technologies make the learning and teaching easier, the contents of some courses will be expanded, a considerable number of new courses will be generated, interdisciplinary courses and studies will be more possible. Students and faculties will contribute together to the development of curriculum.

Modern higher education technologies will also change present instructional methods to a more effective one. The faculties will have to adopt an instructional method best suited to the class of students whom they target or to develop new methods best suited for them based on their feedback. Video conferencing techniques, simulators and on-line access to many practical training kits will revolutionize instructional methods. Information Technology infrastructure in the campus provide quality higher education to students and to provide proper academic and research environment to support University’s endeavor for excellence.

More importantly, these technologies will provide the education and knowledge for these people to become prosperous nations that can fend for themselves and provide for their people. Transfers of technology from the developed world to the developing world will improve the standard of living, increase efficiency in production and become a base for economic growth, without this transfer these countries will fall further into poverty and economic ruin, with little hope for survival. For most people of the developed world, the developing world is not something they concern themselves with; they do not see it everyday and therefore it does not exist. This could not be farther from the truth. The developing world is in need of help but the developed world constantly turns a blind eye. Our current love affair with technology may provide the answer for underdeveloped nations problems. The standard of living is so low in these countries that our everyday conveniences are a struggle for the entire population to obtain. If the developed nations could meet these base needs, these countries may be able to overcome their current problems. The first issue that must be dealt with is the unsatisfactory health care and medical technology.

Most IT organizations still install and maintain computers the same way the automotive industry built cars in the early 1900's: An individual craftsman manually manipulates a machine into being, and manually maintains it afterward. This is expensive. The automotive industry discovered first mass production, then mass customization using standard tooling.

The standards and practices described here are the standarized tooling needed for mass customization within IT. This tooling enables:
• Scalable, flexible, and rapid deployments and changes
• Cost effective, timely return on IT investment
• Low labor headcount
• Secure, trustworthy computing environments
• Reliable enterprise infrastructures

This are the 5 services which Information Technology Infrastructures can give to the University:
1. Service Strategy
As the center and origin point of the ITIL Service Lifecycle, the Service Strategy volume provides guidance on clarification and prioritization of service provider investments in services. More generally, Service Strategy focuses on helping IT organizations improve and develop over the long term. In both cases, Service Strategy relies largely upon a market-driven approach. Key topics covered include service value definition, business case development, service assets, market analysis, and service provider types. Processes covered include service portfolio management, demand management, and IT financial management.

2. Service Design
The ITIL Service Design volume provides good practice guidance on the design of IT services, processes, and other aspects of the service management effort. Significantly, design within ITIL is understood to encompass all elements relevant to technology service delivery, rather than focusing solely on design of the technology itself. As such, Service Design addresses how a planned service solution interacts with the larger business and technical environments, service management systems required to support the service, processes which interacts with the service, technology, and architecture required to support the service, and the supply chain required to support the planned service. Within ITIL, design work for an IT service is aggregated into a single Service Design Package (SDP). Service Design Packages, along with other information about services, are managed within the service catalog. Processes covered in this volume include service level management, availability management, capacity management, IT service continuity management, information security management, supplier management, and service catalog management.

3. Service Transition
Service transition relates to the delivery of services required by the business into live/operational use, and often encompasses the "project" side of IT rather than "BAU" (Business As Usual). This area also covers topics such as managing changes to the "BAU" environment. Topics include Service Asset and Configuration Management, Transition Planning and Support, Release and deployment management, Change Management, Knowledge Management, as well as the key roles of staff engaging in Service Transition.

4. Service Operation
Best practice for achieving the delivery of agreed levels of services both to end-users and the customers (where "customers" refer to those individuals who pay for the service and negotiate the SLAs). Service Operations is the part of the lifecycle where the services and value is actually directly delivered. Also the monitoring of problems and balance between service reliability and cost etc are considered. Topics include balancing conflicting goals (e.g. reliability vs cost etc), Event management, incident management, problem management, request fulfillment, access management, and service desk. The functions include technical management, application management, operations management and Service Desk as well as, responsibilities for staff engaging in Service Operation.

5. Continual Service Improvement (CSI)
Aligning and realigning IT services to changing business needs (because standstill implies decline).
The goal of Continual Service Improvement is to align and realign IT Services to changing business needs by identifying and implementing improvements to the IT services that support the Business Processes. The perspective of CSI on improvement is the business perspective of service quality, even though CSI aims to improve process effectiveness, efficiency and cost effectiveness of the IT processes through the whole lifecycle. To manage improvement, CSI should clearly define what should be controlled and measured.
CSI needs to be treated just like any other service practice. There needs to be upfront planning, training and awareness, ongoing scheduling, roles created, ownership assigned, and activities identified to be successful. CSI must be planned and scheduled as process with defined activities, inputs, outputs, roles and reporting.

Infrastructure Management

ICT Infrastructure Management processes recommend best practice for requirements analysis, planning, design, deployment and ongoing operations management and technical support of an ICT Infrastructure. ("ICT" is an acronym for "Information and Communication Technology".)
The Infrastructure Management processes describe those processes within ITIL that directly relate to the ICT equipment and software that is involved in providing ICT services to customers.
• ICT Design and Planning • ICT Deployment
• ICT Operations
• ICT Technical Support
These disciplines are less well understood than those of Service Management and therefore often some of their content is believed to be covered 'by implication' in Service Management disciplines.

In information technology and on the Internet, infrastructure is the physical hardware used to interconnect computers and users. Infrastructure includes the transmission media, including telephone lines, cable television lines, and satellites and antennas, and also the routers, aggregators, repeaters, and other devices that control transmission paths. Infrastructure also includes the software used to send, receive, and manage the signals that are transmitted.

In some usages, infrastructure refers to interconnecting hardware and software and not to computers and other devices that are interconnected. However, to some information technology users, infrastructure is viewed as everything that supports the flow and processing of information.
Infrastructure companies play a significant part in evolving the Internet, both in terms of where the interconnections are placed and made accessible and in terms of how much information can be carried how quickly.

Service Support
The Service Support discipline is focused on the User of the ICT services and is primarily concerned with ensuring that they have access to the appropriate services to support the business functions.
To a business, customers and users are the entry point to the process model. They get involved in service support by:
• Asking for changes
• Needing communication, updates
• Having difficulties, queries.
• Real process delivery

The service desk is the single contact point for customer’s problems. If there is a direct solution, it tries to resolve the problem. If not, it creates an incident.
Service Desk / Service Request Management
Tasks include handling incidents and requests, and providing an interface for other ITSM processes.
• Single Point of Contact (SPOC) and not necessarily the First Point of Contact (FPOC)
• There is a single point of entry and exit
• Easier for Customers
• Data Integrity
• Communication channel is streamlined

The primary functions of the Service Desk are:
• Incident Control: life cycle management of all Service Requests
• Communication: keeping the customer informed of progress and advising on workarounds

The Service Desk function is known under various names .
• Call Center: main emphasis on professionally handling large call volumes of telephone-based transactions
• Help Desk: manage, co-ordinate and resolve incidents as quickly as possible
• Service Desk: not only handles incidents, problems and questions but also provides an interface for other activities such as change requests, maintenance contracts, software licenses, service level management, configuration management, availability management, Financial Management and IT Services Continuity Management
The three types of structure that can be considered are:
• Local Service Desk: to meet local business needs - is practical only until multiple locations requiring support services are involved
• Central Service Desk: for organizations having multiple locations - reduces operational costs and improves usage of available resources
• Virtual Service Desk: for organizations having multi-country locations - can be situated and accessed from anywhere in the world due to advances in network performance and telecommunications, reducing operational costs and improving usage of available resources

Incident Management
The goal of Incident Management is to restore normal service operation as quickly as possible and minimize the adverse effect on business operations, thus ensuring that the best possible levels of service quality and availability are maintained. 'Normal service operation' is defined here as service operation within Service Level Agreement (SLA) limits.
Problem Management
The goal of 'Problem Management' is to resolve the root cause of incidents and thus to minimize the adverse impact of incidents and problems on business that are caused by errors within the IT infrastructure, and to prevent recurrence of incidents related to these errors. A `problem' is an unknown underlying cause of one or more incidents, and a `known error' is a problem that is successfully diagnosed and for which either a work-around or a permanent resolution has been identified. The CCTA defines problems and known errors as follows:

The problem management process is intended to reduce the number and severity of incidents and problems on the business, and report it in documentation to be available for the first-line and second line of the help desk. The proactive process identifies and resolves problems before incidents occur. These activities are:
• Trend analysis;
• Targeting support action;
• Providing information to the organization.

The Error Control Process is an iterative process to diagnose known errors until they are eliminated by the successful implementation of a change under the control of the Change Management process.
The Problem Control Process aims to handle problems in an efficient way. Problem control identifies the root cause of incidents and reports it to the service desk. Other activities are:
• Problem identification and recording;
• Problem classification;
• Problem investigation and diagnosis.

Change Management
The goal of Change Management is to ensure that standardized methods and procedures are used for efficient handling of all changes,
The main aims of Change Management are:
• Minimal disruption of services
• Reduction in back-out activities
• Economic utilization of resources involved in the change

Change Management Terminology
• Change: the addition, modification or removal of CIs
• Request for Change (RFC): form used to record details of a request for a change and is sent as an input to Change Management by the Change Requestor
• Forward Schedule of Changes (FSC): schedule that contains details of all forthcoming Changes

Release Management
Release Management is used for platform-independent and automated distribution of software and hardware, including license controls across the entire IT infrastructure. Proper software and hardware control ensures the availability of licensed, tested, and version-certified software and hardware, which functions as intended when introduced into existing infrastructure. Quality control during the development and implementation of new hardware and software is also the responsibility of Release Management. This guarantees that all software meets the demands of the business processes. The goals of release management are:
• Plan the rollout of software
• Design and implement procedures for the distribution and installation of changes to IT systems
• Effectively communicate and manage expectations of the customer during the planning and rollout of new releases
• Control the distribution and installation of changes to IT systems
The focus of release management is the protection of the live environment and its services through the use of formal procedures and checks.

Release Categories
A Release consists of the new or changed software and/or hardware required to implement approved changes
Releases are categorized as:
• Major software releases and hardware upgrades, normally containing large amounts of new functionality, some of which may make intervening fixes to problems redundant. A major upgrade or release usually supersedes all preceding minor upgrades, releases and emergency fixes.
• Minor software releases and hardware upgrades, normally containing small enhancements and fixes, some of which may have already been issued as emergency fixes. A minor upgrade or release usually supersedes all preceding emergency fixes.
• Emergency software and hardware fixes, normally containing the corrections to a small number of known problems.

Releases can be divided based on the release unit into:
• Delta Release: is a release of only that part of the software which has been changed. For example, security patches.
• Full Release: means the entire software program is deployed—for example, a new version of an existing application.
• Packaged Release: is a combination of many changes—for example, an operating system image which also contains specific applications.


Sources:
http://en.wikipedia.org/wiki/Information_Technology_Infrastructure_Library#ICT_Infrastructure_Management
http://searchdatacenter.techtarget.com/sDefinition/0,,sid80_gci212346,00.html