Managerial Issues
Ernest Odel
CMGT 445
05/12/2014
Mike Goyden

Managerial Issues Citizens demand an assortment of fundamental municipal services like cleanliness, sanctuary, transportation, condition of energy and water, and etc., to be supplied by the city and or state that they reside in. Any region where one resides in requires a sustained infrastructure which necessitates the technical arrangements helping with the provision of services. “The infrastructure of a city, for example, includes not only components such as streets and power, telephone, water, and sewage lines, but also schools, retail stores, and law enforcement.” Similarly, indispensable personnel frequently choose organizations with superior amenities, management, and business processes. The goal of this paper is to list and discuss the managerial issues associated with managing an organization’s IS infrastructure. The topics that will be covered include the information related to configuration management and preventative maintenance, the industry standards in configuration management and control, the training approaches to allow for adaptive maintenance and confidence and the effect of globalization on managing and IS infrastructure. The infrastructure components of an information system consists of computer hardware software, communication and collaboration networks, databases, facilities, and human resources to sustain the network personnel’s decision making, business procedures, as well as their competitive strategy. On maximum heights, establishments depend on three indispensable capabilities sustained by information systems which are the processing, storage, and transmission of data. Consequently, the majority of organization’s daily business procedures rely on the fundamental IS infrastructure, although to diverse degrees of course. For instance, “an organization’s management needs an infrastructure to support a variety of activities, including reliable communication networks to support collaboration between suppliers and customers, accurate and timely data and knowledge to gain business intelligence, and information systems to aid decision making and support business processes.” The conventional software configuration management procedure is looked at by the practitioners as the finest resolution to dealing with changes within software projects because it recognizes the functional and physical characteristics of software at different instances at a time and executes systematic power of changes to discover characteristics for the principle of sustaining the software’s veracity and traceability from beginning to end of the software development life cycle (SDLC). The software configuration management (CSCM) procedure describes the need to map out alteration, and the capability to substantiate that the last distributed software contains all of the intended improvements that are believed to be integrated in the release. It characterizes four processes that have to be defined for every software project to guarantee that it identifies four procedures that must be defined for each software project to ensure that a reliable CSCM process is put into operation. Those four procedures are: 1. Configuration identification 2. Configuration control 3. Configuration status accounting and 4. Configuration audits These conditions and characterizations modify from level to level, but are fundamentally identical. Presently, the International Standards Organization (ISO) does not contain an official procedure for configuration management despite the fact that quality management necessitates tracking documentation as well as alterations to parts. ISO standard 10007 gives an array of suggestions “for change management and a quality management system to retain control over change requests ISO 10007 gives recommendations on how to perform configuration status accounting, the ability to report the baseline configuration of a part structure or document structure for any given date. ISO 10007 also recommends that companies perform configuration audits to ensure the configuration of products when they are built or shipped.” There is no computer system once it has been put into operation stay put unchanged through the remainder of its working life. Alterations are always made, and safeguarding is undertaken. If clients of a computer system are to expand their skills and encompass self-reliance in the computing infrastructure that they are using, there must be training and support provided to them so they’ll have the skills and instruments to build self-confidence. Having the proper documentation for users is imperative but not satisfactory alone, the users require plenty of practice like anything else when learning something new as well as needing a muscular support for organization to maintain the system working with most advantageous execution. “Adaptive maintenance refers to changes made to a system to evolve its functionality to changing business needs or technologies. Changes made to a system to add new features or to improve performance are perfective maintenance changes. Changes made to a system to avoid possible future problems are preventive maintenance changes.” Technology and inexpensive admission to power have changed the manner the globe does all business, by condensing the costs of particular kinds of business-to-business dealings. The decreased transaction overheads, motivated by alteration in the government policies and enhanced interactions infrastructure, have led to a broad assortment of business practices are referred to as globalization. “Globalization may offer enterprises exciting new growth opportunities in emerging markets, but it can also introduce a complex array of operational risks. The challenge is that without the right infrastructure in place to confront these risks, international projects can immobilize an organization and lead to the biggest consequence of all—putting the company out of business.”

References:

Lopes, M. (2013, May 6). Five Globalization Risks and How to Manage Them. . Retrieved May 11, 2014, from https://blogs.oracle.com/eppm/entry/five_globalization_risks_and_how

Onuoha, O., J.O, O., & Benson, E. (2012, January 3). COMPUTER SYSTEM CONFIGURATION MANAGEMENT. . Retrieved May 11, 2014, from http://dspace.covenantuniversity.edu.ng/bitstream/handle/123456789/146/Computer%20System%20Configuration%20Management.pdf?sequence=1

Valacich, J., & Schneider, C. (2012). Managing the Information Systems Infrastructure and Services. Information Systems Today: Managing in the Digital World (). : Prentice Hall.

Wilhite, T. (2012, December 11). Industry Standards for Configuration Management and Change Management. . Retrieved May 11, 2014, from http://tamarawilhite.hubpages.com/hub/Industrial-Standards-for-Configuration-Management-and-Change-Management