Information Technology Capstone Project Part I: Data Warehousing and Offshore Development

Project Introduction

The Project Introduction herein documents the fundamental state of the case scenario organization, an innovative internet-based company prior to enhancements. The following five basic components capture the content of the introductory portion of the project. They include: a) Background of the company, b) Details pertaining to the company's business activities, c) Speculation on outsourcing and offshoring opportunities, d) Description about current information systems company has to support the business, and e) Overview of systemic business supports which involve operational systems, databases, data warehousing, cloud technology/virtualization, and network infrastructure and security.

Company Background

The working case scenario and supposition is such that this investigator is functioning as Chief Information Officer (CIO) of an innovative internet-based company, revenues in excess of $35 million to merge with a multinational firm. The responsibility entails development to strategically integrate all systems technologies, including understanding the restraints and assumptions to cloud technology security implementation and protocols, with a 60-day delivery plan for final expansion to be realized in a 6-month period. The goal to redesign the physicality and promote a successful re-identification of new merger objectives within the rubric of IT tools applications is formidable. Yet with the right combination certain budgetary parameters using cutting edge hardware/software to reshape the network will ensure efficiency, proper prioritization, address of security threats, and smooth transition towards best practices in excellent leadership in management. 

Company Business Activity Details

Some major factors to consider involve current revenues around $35 million, a 60-day time frame to plan delivery/presentation, a 6-month window to the finalization of all merger infrastructure and data implementation, and special attention to physical expansion to three floors. Design data warehousing solutions may best meet merged company needs by building it for ease of end-users and to not go offshore with this component. One detail considers automating the Sarbanes-Oxley compliance regulations for executives as suggests recognized father of data warehousing Inmon. 

Basics demands involve details of:

– Choosing a new site for architectural consideration

– Deciding new integrative managerial relationships/duties

– An additional strategy to greatly and reduce temper costs

– Choose a hybrid model for the meeting hosted versus on-site solution

Outsourcing & Offshoring Speculations

Outsourcing and supplier issues are critical. You must go beyond the organizational mapping of drawing boxes and lines. Inmon (2004) suggests reasons not to go offshore in the area of data warehousing because warehouses are unique to each company, offshoring handles processes better, the environment requirements are “never firm” (p. 52). Essentially, your data warehousing is the central nervous system.

Current IT Systems Descriptive Supports & Overview

– Operational systems: create tight command/control with calculated reliability, enhance R&D team

– Databases: decide data mining, robotics, electronic monitoring standards, adhering to SDLC lifecycle

– Data Warehousing: concept/design, deployment, size, unstructured data, exploring, ODS & recovery

– Cloud Computing Technology: transmission cryptography, specific strategies to streamline operations, workforce task management, customer analytics, and general digital media management

– Network Infrastructure & Security: design strategy for process and people, hierarchical degrees of access, best fit for new organizational context/effectiveness, adopt risk management and security procedures implementation and training, and update departmental processes periodically.

Reference

Inmon, B. (2004). Straight talk: Data warehousing and offshore development. DM Review, 14(1), 52-53.