IMPLEMENTATION PLAN 1INTRODUCTION 1. 1Purpose The implementation plan has been developed to support the strategic plan of the Attendance Monitoring System. The implementation plan will be amended and updated as new actions are introduced and as developments are implemented to the system. The system tracks the performance of employees regarding their attendance on a daily basis. 1. 2System Overview
Attendance Monitoring System provides a foolproof solution using fingerprint authentication with the use of a Barcode Scanner for input and affiliated with payroll system and human resource development system and provides efficient reports of the company.. The system records details such as arrival and departure of employees besides monitoring their attendance on a daily basis. 1. 2. 1System Description Attendance Monitoring System takes input in a barcode scanner to collect and process data. Attendance monitoring system will provide the needed data for the payroll system for the deductions of the employee to be process.
It provides reports of the DTR, the absences, and the leave of the employee. 1. 2. 2System Organization Attendance Monitoring System has a barcode scanner that takes the input of the employee in barcode id. The system will monitor the daily, monthly, yearly record of the employee’s absences, leaves, and DTR. It computes for the late of the employee for the deductions. 1. 3Project References •http://www. digitscorp. com/insight/attendance-and-time-monitoring-system. html •http://www. bioenable. co. in/fingerprints_software_development_kit. htm •http://www. aryah. net/TAMS. htm 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 subsequent sections provide a brief description of the implementation and major tasks involved in this section. 2. 1Description of Implementation This section provides a brief description of the system and the planned deployment, installation, and implementation approach. * The Attendance Monitoring System will be implemented along together with the Human Resource Development Information System and Payroll System, in which it can operate as a single software. . 2Points 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. 3Major 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: What the task will accomplish •Resources required to accomplish the task •Key person(s) responsible for the task •Criteria for successful completion of the task •Examples of major tasks are the following: •Providing overall planning and coordination for the implementation •Providing appropriate training for personnel •Ensuring that all manuals applicable to the implementation effort are available when needed •Providing all needed technical assistance •Scheduling any special computer processing required for the implementation •Performing site surveys before implementation Ensuring that all prerequisites have been fulfilled before the implementation date •Providing personnel for the implementation team •Acquiring special hardware or software •Performing data conversion before loading data into the system •Preparing site facilities for implementation 2. 4Implementation 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. 5Security
If appropriate for the system to be implemented, include an overview of the system security features and requirements during the implementation. 2. 5. 1System 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. 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. 3IMPLEMENTATION SUPPORT 3. 1Hardware, Software, Facilities, and Materials The following are hardware devices and softwares which are essential to run the Attendance Monitoring System:
Hardware: Working PC Units Barcode Reader Device Fingerprint Scanner Printing Devices Software: Apache XAMPP 3. 1. 1Hardware Working PC Units -Having working units is a necessary, for it is the main device that will hold the whole proposed system, particularly the Attendance Monitoring System. Barcode Reader Device -The barcode reader is the device that will verify whether an employee’s identification card’s number is in fact an official employee of a certain company. -It will also confirm whether his / her identification number matches anyone in the system’s database
Fingerprint Scanner -The fingerprint scanner will serve as an additional security device for employees who logs in or logs out of the system. -It will test whether there is an existing fingerprint copy that will match the employee’s identification number. Printing Devices -Printing devices are also important in having this kind of system. Its main function is to be able to print reports for their Employee’s Daily Time Record, Absences, Tardiness and Leave. 3. 1. 2Software Apache XAMPP – This software is mainly used to contain the system’s database.
From this software they will be able to retrieve information regarding an employee’s attendance 3. 1. 3Facilities Server’s or Administrator’s Room – This main facility will be the focal room where the system is contained. There will be administrator(s) who will manage the whole system. Training Halls – For the Attendance Monitoring System, a room that can accommodate two (2) to five (5) personnel is enough to provide training in implementing this system software. Normally, two (2) to three (3) administrators are sufficient to run an attendance system. But it also depends on how big the company is. Training Wise After the installation of the said system, thirty (30) to forty (40) days of training is more than enough to run the system properly and to master its features. A maximum of two (2) to three (3) hours of training can be allotted each day for the mastery of the system. 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 known or proposed staffing requirements, if appropriate. Also describe the training, if any, to be provided for the implementation staff. 3. 2. 1Personnel 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. 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. Describe 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 modification 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. 3Performance 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 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. 1Post-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.
