Implementation Planning for DaimlerChrysler - Case Study Example

Implementation Plan al Affiliation INTRODUCTION The purpose of this paper is to draft an implementation plan for installing a new information system for the DaimlerChrysler (DC) Company. The current system operated by the organization is not integrated with all the essential components of the entire company network. That is why the current audit has revealed major gaps within the current information system that have to be resolved in order to streamline the business processes. The implementation proposal aims to lift up the organization’s value through minimizing operational costs by cutting down on unnecessary budgets and spending (Crespi, Criscuolo & Haskell, 2007). This design of the proposed system will save on cost and subsequently increase the profit margins by the end of the financial year. The implementation report will also highlight on the systems approach for building a technological software application that universally integrates all the end user entities within a central information system. Automation of this project passes will go through specific software development phases. These processes start from feeling the need of automation (Requirement analysis) to reaping the benefits of automation (project execution) within the proposed environment. In huge organizations like the DaimlerChrysler (DC) Company the implementation partners in this project have to be kept informed in order to ensure a fruitful completion of the implementation plan. A poor implementation in important IT project like this one may result in big operational troubles, huge business loss or even closure of operations. Identifying and examining the business goals of this project form the basis for achieving the objectives of the IT project proposed for the DaimlerChrysler (DC) Company. GOALS AND OBJECTIVES The project goals and objectives mainly define the sole purpose for carrying out the implementation of the technology project. The objectives of this implementation plan can be divided into two sections, namely: Business Goals and Objectives The business goals of this project aim to solve the problems described in the case study reading provided in the problem statement. Some of the business goals that have been identified include: Simplify the management of information The sharing of technical and general information, for example, the CATIA files can be easily communicated to both internal and external entities authorized to participate or interact with the organization’s system. Increase profits by reducing operating costs Reducing operating costs by majorly focusing on reducing the by increasing efficiency and increasing revenues Enhances the ability and effectiveness of staff to perform their jobs The involved staff majorly includes the suppliers, the plant managers and the low level staff in the organization. The effectiveness of communication between them streamlines business processes. Eliminate redundant data entry throughout the organization This eliminated the need for application reuse within the system. This saves on costs. Project Goals and Objectives 1. Organize the entire company operations into database system Unifying all the company employees to operate within a single platform system facilitates easy information monitoring that can be used for future decision making activities. 2. Increase efficiency This is achieved via consolidating activities for the various entities involved with the system. For example, the time for suppliers to make and receive approval orders for mechanical is greatly reduced. 3. Provides high levels of data security. Promote a system data storage project that stores, updates and secures the information on a central database accessible to the authorized system administrators and company stakeholders. 4. Facilitate coordinated crime prevention and reduction Operating a universal or unified system that can be monitored from a central or remote location by a system admin facilitates reducing corruption or fraud that might occur at individual sub locations not connected to the system. 5. Provides an open, flexible, reliable technology base for the future System reliability, consistency and flexibility are vital to any technological project to be successful. This is because these aspects form basis for the future progression of the organization. SCOPE OF THE PROJECT Scope Definition Implementing the project scope necessitates the devotion of the project leader to consolidate and control the project team members accountable for completing this project. The project parameters or scope defines the workload that has to be completed to deliver the end product expected from this project. The scope of the project also aims to describe the estimated business outcomes that hold positive features and functions for the proposed system (Schwalbe, 2010). For instance, the system aims to automate connection between the managers and employers or the suppliers to the product distributors. It will also introduce the latest technology into the business operating environment. For example, automate digital CAD (computer aided design), internet messaging alerts and exchange of files or reports among the staff. PROJECTED COURSE AND EXPENSES System Development Life Cycle The selected System Development Life Cycle for this particular implementation plan utilized the Waterfall project development technique. The Waterfall software development life cycle entails the following phases: 1. Requirements Analysis – The collection of relevant information from end user entities to determine the additional core components of the anticipated system. 2. Design phase – entails the emulation of design application structures and the hard coding of the systems back end sore code. 3. Implementation – involves executing the system program in the organizations network. 4. Testing phase – majorly involves testing the developed application in the intended environment and monitor how the human interact with it. 5. Installation and Maintenance - Successful testing leads to installation and finally the activated operation of the system in the organization. Constant maintenance is required to identify and fix bugs or flaws that might come up. The Waterfall SDLC Model Project Schedule (Gant Chart) A project schedule showcases the scope of activities and the time framework expected to complete the various project milestones set by the project management team. Assigning tasks to each individual according to their specialization while sustaining constant or periodical observations on the activities ensures there is no time wasted on unnecessary project deliverables. The chart below represents the time frame and pointers that have to be addressed. ACTION Time (Weeks) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 Project detail description Project proposal Literature review Project plan Functional specification Design phase Coding System testing System Implementation Documentation Projected Budget for resources needed ACTIVITY ESTIMATED COST Hardware and software system installation for all PCs in the company $ 3600000 Server Space acquisition $ 100000 Travelling costs $ 300000 Research costs $ 400000 Internet $ 300000 Travelling costs $ 350000 Insurance/Miscellaneous $ 300000 Staff Training $ 300000 Project Team Group Management $ 500000 System Care and Maintenance in 1st year operation $1000000 TOTAL $ 7,150,000 Milestones to be achieved Milestone to be achieved Objectives Responsible Individual Conduct interviews/fill in questionnaires with top level managers and low level staff Objective 1: Collect system requirements information for proposed system Team member 5 Test the interface consistency for the designed system Objective 2:Test Design Team member 2 Compile source code Objective 3:Complete Coding Team member 4 Design admin interfaces Objective 4: Interface design Team member 3 Execute files in the network Acquire customized domain name services Objective 5: Implement system Team member 4 Upload content to server Objective 6: Install system Team member 4 Constantly monitor the system functionality Objective 7: Maintain the system Team member 2 ASSUMPTIONS One of the assumptions of implementing this program is that the Information System would be readily accepted into its operating environment by all the end user entities. Additionally, it is assumed that most of the system functionality will be easily understood by its end users in order to facilitate fast and easy operation (Young & Burgess, 2010). Another assumption taken is that a positive ROI would be realized as soon as possible after the system is installed and is fully operating within the organization. CONSTRAINTS Project Constraints Delayed information passing and getting feedback information in time is a major constraint experienced during the project plan implementation. Deferred communication limits the team from moving forward to a subsequent phase of the project. Another constraint to the project would be the delayed release of funding for the proposed budget and expenses. This also affects the project progress negatively since resource acquisition is hindered. Critical Project Barriers The major barrier to the success of the implementation of this project is the possibility of the old generation not accepting the new product. Folks within the organization might still be hang on the previous information system and would be reluctant to move forward. Therefore convicting them to accept the new system is a difficult task for the project management team. The time frame for accomplishing the project accomplishing the project would be limited to cover all the components for the system. The system use is intended for a wide geographical area and individuals from different nations. Thus, incorporating language modules, security layers and protocols that serve all the objects of the system will prove to be an uphill task. REFERENCES Ashurst, C. (2011). Benefits realization from information technology. Basingstoke [etc.: Palgrave Macmillan. Chew, E. K., & Gottschalk, P. (2009). Information technology strategy and management: Best practices. Hershey: Information Science Reference. Crespi, G., Criscuolo, C., & Haskell, J. (2007). Information technology, organisational change and productivity. London: Centre for Economic Policy Research. Schwalbe, K. (2010). Information technology Project Management. Boston, MA: Course Technology/Cengage Learning. Tsai, H.-L. (2003). Information technology and business process reengineering: New perspectives and strategies. Westport Conn.: Praeger. Young, L., & Burgess, B. (2010). Marketing technology as a service: Proven techniques that create value. Hoboken, N.J: Wiley. Read More