Assignment 2: LASA 1—Business Analytics Implementation Plan Part 1 In learning a
ID: 2746052 • Letter: A
Question
Assignment 2: LASA 1—Business Analytics Implementation Plan Part 1
In learning about BA, you have covered quite a few topics from the manager’s decision-making process to technology integration. The best way to pull all of this knowledge together is to create a BA implementation plan for a hypothetical organization. This is something you would do in a real-life scenario if you came across an organization that does not utilize BA; as a professional, you would create the plan and then present it to management.
Description of LASA
In this assignment, you will create a business analytics implementation plan. The plan will consist of explaining business analytics to management, addressing the advantages and disadvantages of business analytics, the challenges of utilizing business analytics, along with a backup plan in case management does not accept the first option.
Scenario
You have been hired as a business analyst for a well-known design firm. Currently, they utilize technology for their day-to-day operations but not to analyze data to help with making business decisions. Your task is to convince management that the usage of business analytics would be a great benefit to the business and it would help the business to make well-informed decisions and thus action plans that would align with the business’s strategic planning.
The firm currently has technology in place but does not have any connected systems. The databases are all independent of each other but they do utilize a client/server environment. The firm currently has one location and it is looking to add a second location in another part of the state, but is unsure as to whether it would be beneficial to the firm.
Instructions
Using the Argosy University online library resources and the Internet, research business analytics implementation plans. Select at least 4 scholarly sources for use in this assignment.
Write a proposal in which you explain the importance of using business analytics.
Objectives of proposals:
Describe the business and provide a summary of the business analytics they could apply to their business in multiple scenarios.
Describe the benefits and disadvantages of business analytics, as well as how the organization can be proactive in addressing any disadvantages. Include at least 3 benefits and disadvantages.
Address any challenges the organization may face using business analytics, as well as how the organization can be proactive in addressing the challenges. Be sure to address at least 3 challenges.
Propose three business analytic techniques. Compare them and discuss at least two benefits and disadvantages of each.
Create an implementation plan to integrate business analytics into your organization.
Create a backup proposal in case management does not approve your initial proposal. The backup proposal should have at least 3 changes different from the original plan.
Write the paper from the perspective that it will be presented to management of the firm and you are trying to persuade them to utilize business analytics for data-driven decision making.
The paper has to contain the following:
Cover Page
Table of Contents (auto-generated by MS Word)
Introduction
Implementation Plan (5–6 pages of content)
Conclusion
References
Utilize at least 4 scholarly sources in support of your recommendations.
Explanation / Answer
Implementation Plan
The Implementation Plan describes how the information system will be deployed, installed and transitioned into an operational system. The plan contains an overview of the system, a brief description of the major tasks involved in the implementation, the overall resources needed to support the implementation effort (such as hardware, software. facilities, materials, and personnel), and any site-specific implementation requirements. The plan is developed during the Design Phase and is updated during the Development Phase; the final version is provided in the Integration and Test Phase and is used for guidance during the Implementation Phase. The outline shows the structure of the Implementation Plan.
1 INTRODUCTION
This section provides an overview of the information system and includes any additional information that may be appropriate.
1.1 Purpose
This section describes tile purpose of the Implementation Plan. Reference the system name and identify information about the system to be implemented.
1.2 System Overview
This section provides a brief overview of the system to be implemented, including a description of the system and its organization.
1.2.1 System Description
This section provides an overview of the processes the system is intended to support. If the system is a database or an information system, provide a general discussion of the description of the type of data maintained and the operational sources and uses of those data.
1.2.2 System Organization
This section provides a brief description of system structure and the major system components essential to the implementation of the system. It should describe both hardware and software, as appropriate. Charts, diagrams, and graphics may be included as necessary.
1.3 Project References
This section provides a bibliography of key project references and deliverables that have been produced before this point in the project development.
1.4 Glossary
Provide a glossary of all terms and abbreviations used in the manual. If it is several pages in length, it may be placed in an appendix.
2 MANAGEMENT OVERVIEW
The subsequent sections provide a brief description of the implementation and major tasks involved in this section.
2.1 Description of Implementation
This section provides a brief description of the system and the planned deployment, installation, and implementation approach.
2.2 Points of Contact
In this section, identify the System Proponent, the name of the responsible organization(s), and titles and telephone numbers of the staff who serve as points of contact for the system implementation. These points of contact could include the Project Manager. Program Manager, Security Manager. Database Administrator, Configuration Management Manager, or other managers with responsibilities relating to the system implementation. The site implementation representative for each field installation or implementation site should also he included, if appropriate. List all managers and staff with whom the implementation must be coordinated.
2.3 Major Tasks
This section provides a brief description of each major task required for the implementation of the system. Add as many subsections as necessary to this section to describe all the major tasks adequately. The tasks described in this section are not site-specific, but generic or overall project tasks that are required to install hardware and software, prepare data, and verify the system. Include the following information for the description of each major task, if appropriate:
2.4 Implementation Schedule
In this section, provide a schedule of activities to be accomplished during implementation. Show the required tasks (described in Section 2.3, Major Tasks) in chronological order, with the beginning and end dates of each task.
2.5 Security
If appropriate for the system to be implemented, include an overview of the system security features and requirements during the implementation.
2.5.1 System Security Features
In this section, provide an overview and discussion of the security features that will be associated with the system when it is implemented. It should include the primary security features associated with the system hardware and software. Security and protection of sensitive bureau data and information should be discussed, if applicable. Reference the sections of previous deliverables that address system security issues, if appropriate.
2.5.2 Security During Implementation
This section addresses security issues specifically related to the implementation effort, if any. For example, if LAN servers or workstations will he installed at a site with sensitive data preloaded on non-removable hard disk drives, address how security would be provided for the data on these devices during shipping, transport, and installation because theft of the devices could compromise the sensitive data.
3 IMPLEMENTATION SUPPORT
This section describes the support software, materials, equipment, and facilities required for the implementation, as well as the personnel requirements and training necessary for the implementation. The information provided in this section is not site-specific. If there arc additional support requirements not covered by the subsequent sections, others may be added as needed.
3.1 Hardware, Software, Facilities, and Materials
In this section, list support software, materials, equipment, and facilities required for the implementation, if any.
3.1.1 Hardware
This section provides a list of support equipment and includes all hardware used for testing time implementation. For example, if a client/server database is implemented on a LAN, a network monitor or “sniffer” might be used, along with test programs. to determine the performance of the database and LAN at high-utilization rates. If the equipment is site-specific, list it in Section 4, Implementation Requirements by Site.
3.1.2 Software
This section provides a list of software and databases required to support the implementation. Identify the software by name, code, or acronym. Identify which software is commercial off-the-shelf and which is State-specific. Identify any software used to facilitate the implementation process. If the software is site-specific, list it in Section 4.
3.1.3 Facilities
In this section, identify the physical facilities and accommodations required during implementation. Examples include physical workspace for assembling and testing hardware components, desk space for software installers, and classroom space for training the implementation stall. Specify the hours per day needed, number of days, and anticipated dates. If the facilities needed are site-specific, provide this information in Section 4, Implementation Requirements by Site.
3.1.4 Material
This section provides a list of required support materials, such as magnetic tapes and disk packs.
3.2 Personnel
This section describes personnel requirements and any known or proposed staffing requirements, if appropriate. Also describe the training, if any, to be provided for the implementation staff.
3.2.1 Personnel Requirements and Staffing
In this section, describe the number of personnel, length of time needed, types of skills, and skill levels for the staff required during the implementation period. If particular staff members have been selected or proposed for the implementation, identify them and their roles in the implementation.
3.2.2 Training of Implementation Staff
This section addresses the training, if any, necessary to prepare staff for implementing and maintaining the system; it does not address user training, which is the subject of the Training Plan. Describe the type and amount of training required for each of the following areas, if appropriate, for the system:
Present a training curriculum listing the courses that will be provided, a course sequence. and a proposed schedule. If appropriate, identify which courses particular types of staff should attend by job position description.
If training will be provided by one or more commercial vendors, identify them, the course name(s), and a brief description of the course content.
If the training will be provided by State staff, provide the course name(s) and an outline of the content of each course. Identify the resources, support materials, and proposed instructors required to teach the course(s).
3.3 Performance Monitoring
This section describes the performance monitoring tool and techniques and how it will be used to help decide if the implementation is successful.
3.4 Configuration Management Interface
This section describes the interactions required with the Configuration Management (CM) representative on CM-related issues, such as when software listings will be distributed, and how to confirm that libraries have been moved from the development to the production environment.
4 IMPLEMENTATION REQUIREMENTS BY SITE
This section describes specific implementation requirements and procedures. If these requirements and procedures differ by site, repeat these subsections for each site; if they are the same for each site, or if there is only one implementation site, use these subsections only once. The “X” in the subsection number should be replaced with a sequenced number beginning with I. Each subsection with the same value of “X” is associated with the same implementation site. If a complete set of subsections will be associated with each implementation site, then “X” is assigned a new value for each site.
4.1 Site Name or identification for Site X
This section provides the name of the specific site or sites to be discussed in the subsequent sections.
4.1.1 Site Requirements
This section defines the requirements that must he met for the orderly implementation of the system and describes the hardware, software, and site-specific facilities requirements for this area.
Any site requirements that do not fall into the following three categories and were not described in Section 3, Implementation Support, may be described in this section, or other subsections may be added following Facilities Requirements below:
4.1.2 Site implementation Details
This section addresses the specifics of the implementation for this site. Include a description of the implementation team, schedule, procedures, and database and data updates. This section should also provide information on the following:
If the site operations startup is an important factor in the implementation, then address startup procedures in some detail. If the system will replace an already operating system, then address the startup and cutover processes in detail. If there is a period of parallel operations with an existing system, address the startup procedures that include technical and operations support during the parallel cycle and the consistency of data within the databases of the two systems.
- Control inputs
- Operating instructions
- Database data sources and inputs
- Output reports
- Restart and recovery procedures
4.1.3 Back-Off Plan
This section specifies when to make the go/no go decision and the factors to be included in making the decision. The plan then goes on to provide a detailed list of steps and actions required to restore the site to the original, pre-conversion condition,
4.1.4 Post-Implementation Verification
This section describes the process for reviewing the implementation and deciding if it was successful. It describes how an action item list will be created to rectify any noted discrepancies. It also references the Back-Off Plan for instructions on how to back-out the installation, if, as a result of the post-implementation verification, a no-go decision is made.