Implementation Plan

IMPLEMENTATION Plocal area ne 2rk Overview The execution cast accounts how the entropy schema departing be deployed, installed and transitioned into an operational formation. The plan contains an overview of the trunk, a picture ex slur of the major tasks involved in the execution, the overall resources needed to retain the instruction execution struggle (such(prenominal)(prenominal) as ironware, computer software. facilities, materials, and personnel), and any site-specific slaying requirements.The plan is developed during the Design physique and is updated during the Development Phase the final version is provided in the Integration and tally Phase and is delectationd for guidance during the carrying out Phase. The outline shows the structure of the writ of execution Plan. 1INTRODUCTION This variance provides an overview of the nurture brass and takes any additional information that may be appropriate. 1. 1Purpose This divide keys tile purpose of the Implementation Plan. Reference the system name and identify information about the system to be implemented. 1. 2System OverviewThis piece provides a picture overview of the system to be implemented, including a description of the system and its organization. 1. 2. 1System 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 token of data maintained and the operational sources and uses of those data. 1. 2. 2System Organization This section provides a brief description of system structure and the major system components essential to the executing of the system.It should describe both heavy(a)ware and software, as appropriate. Charts, diagrams, and graphics may be include as necessary. 1. 3Project References This section provides a bibliography of key project references and deliverables that stand been produced before this po int in the project development. 1. 4Glossary 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. 2MANAGEMENT OVERVIEW The concomitant sections provide a brief description of the capital punishment and major tasks involved in this section. 2. Description of Implementation This section provides a brief description of the system and the planned deployment, trigger, and death penalty approach. 2. 2Points of Contact In this section, identify the System Proponent, the name of the responsible organization(s), and titles and peal numbers of the staff who serve as points of tactile sensation for the system murder. These points of contact could include the Project Manager. Program Manager, Security Manager. Database Administrator, Configuration Management Manager, or early(a) managers with responsibilities relating to the system implementation.The site implementation representative for to each one welkin installation or implementation site should in any case he included, if appropriate. itemization all managers and staff with whom the implementation must be coordinated. 2. 3Major Tasks This section provides a brief description of each major task needed for the implementation of the system. Add as many subsections as necessary to this section to describe all the major tasks adequately. The tasks exposit in this section are non site-specific, but generic or overall project tasks that are infallible to install hardware and software, prepare data, and verify the system.let in the following information for the description of each major task, if appropriate What the task volition accomplish Resources unavoidable to accomplish the task Key person(s) responsible for the task Criteria for successful finish of the task Examples of major tasks are the following Providing overall planning and coordination for the implementation Providing appropriate culture for personnel Ensuri ng that all manuals applicable to the implementation effort are easy when needed Providing all needed technical avail Scheduling any special computer processing required for the implementation Performing site surveys before implementation Ensuring that all prerequisites have been effect before the implementation date Providing personnel for the implementation aggroup acquiring special hardware or software Performing data rebirth before loading data into the system Preparing site facilities for implementation 2. 4Implementation document In this section, provide a schedule of activities to be accomplished during implementation. memorialize the required tasks (described in Section 2. , Major Tasks) in chronological order, with the first gear and end dates of each task. 2. 5Security If appropriate for the system to be implemented, include an overview of the system security department features and requirements during the implementation. 2. 5. 1System Security Features In this se ction, 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 verbalize system security issues, if appropriate. 2. 5. 2Security 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. 3IMPLEMENTATION SUPPORTThis section describes the support software, materials, equipment, and facilities requir ed for the implementation, as well as the personnel requirements and training necessary for the implementation. The information provided in this section is non site-specific. If there arc additional support requirements non covered by the subsequent sections, others may be added as needed. 3. 1Hardware, Software, Facilities, and Materials In this section, angle of inclination support software, materials, equipment, and facilities required for the implementation, if any. 3. 1. 1HardwareThis section provides a lean of support equipment and includes all hardware used for testing time implementation. For example, if a guest/server database is implemented on a LAN, a network supervise or sniffer might be used, along with test programs. to determine the capital punishment 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. 2Software This section provides a list of software and databas es required to support the implementation. diagnose the software by name, code, or acronym. nominate 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. 3Facilities 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 evaluate dates.If the facilities needed are site-specific, provide this information in Section 4, Implementation Requirements by Site. 3. 1. 4Material This section provides a list of required support materials, such as magnetic tapes and disk packs. 3. 2Personnel This section describes personnel requirements and any cognise or proposed staffi ng requirements, if appropriate. Also describe the training, if any, to be provided for the implementation staff. 3. 2. 1Personnel Requirements and runging In this section, describe the number of personnel, length of time needed, types of skills, and skill levels for the staff required during the mplementation period. If peculiar(prenominal) staff members have been selected or proposed for the implementation, identify them and their roles in the implementation. 3. 2. 2Training 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. trace the type and amount of training required for each of the following areas, if appropriate, for the system System hardware/software installation System support System maintenance and modificationPresent a training curriculum listing the crinkles that will be provided, a consort 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 determine the course(s). 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. 4Configuration Management user 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 go from the development to the production environ ment. 4IMPLEMENTATION 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 said(prenominal) 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, accordingly X is assigned a overbold value for each site. 4. 1Site Name or identification for Site XThis section provides the name of the specific site or sites to be discussed in the subsequent sections. 4. 1. 1Site 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 facilit ies requirements for this area. whatever 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 downstairs Hardware Requirements hound the site-specific hardware requirements necessary to support the implementation (such as. LAN hardware for a client/server database designed to run on a LAN). Software Requirements Describe any software required to implement the system (such as, software specifically designed for automating the installation process). Data Requirements Describe specific data preparation requirements and data that must be available for the system implementation. An example would be the assignment of individual IDs associated with data preparation. Facilities Requirements Describe the site-specific physical facilities and accommodations required during the system implementation period. S ome examples of this type of information are provided in Section 3. 4. 1. 2Site 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 TeamIf an implementation team is required, describe its composition and the tasks to be performed at this site by each team member. ScheduleProvide a schedule of activities, including planning and preparation, to be accomplished during implementation at this site. Describe the required tasks in chronological order with the beginning and end dates of each task. If appropriate, charts and graphics may be used to present the schedule. ProceduresProvide a sequence of circumstantial procedures required to accomplish the specific hardware and software implementation at this site. If necessary, other documents may be referenced. If appropriate, include a step-by-step sequence of the detailed procedures.A checklist of the installation events may he provided to record the results of the process. 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 gibe 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. DatabaseDescribe the database environment where the software system and the database(s), if any, will be installed. Include a description of the different types of database and library environments (such as, production, test, and training databases). Include the horde computer database operating procedures, database file and library naming conventions, database system mu ltiplication parameters, and any other information needed to effectively establish the system database environment. Include database administration procedures for testing changes, if any, to the database management system before the system implementation. Data UpdateIf data update procedures are described in another document, such as the operations manual or diversity plan, that document may be referenced here. The following are examples of information to be included -Control inputs -Operating instructions -Database data sources and inputs -Output reports -Restart and recovery procedures 4. 1. 3Back-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. 4Post-Implementation verification This section describes the process for reviewing the implementation and deciding if i t 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.