Database Implementation Plan for Riordan Manufacturing

Database Implementation Plan for Riordan Manufacturing Riordan Manufacturing has asked our firm, LTB and Associates, to develop a web- base computer program to be subroutined as a Business-to-Business web site in dedicate to purchase materials from their vendors. We wee-wee examined Riordans products and transmission line arrangements, interviewed Riordans employees, and have impelled the best course of action to implement the computer programme. Riordan Manufacturing is a plastics manufacturer based in s everal locations across the world.With three plants based in the Continental US, which atomic number 18 located in Alb whatever, Georgia Pontiac Michigan and in San Jose, California, which is the follow headquarters. A fourth plant is located in Hangzhou, China leave behind non be department of the plan as they purchase materials locally. This where we rationalize how the entropybase leave be set up. Refer to the ERD, Sequence diagram, Use study diagram, and Class D iagram that follow pic pic The following paragraphs leave behind describe the considerations that Riordan Manufacturing countenance need to make in implementing the studybase plan.Database Management System and DataWhere ever it is possible to for our firm to do so, LTB and Associates pass on make a passport on the choice to make. In order to implement the database properly, these recommendations should be use in order to offer the tigh screen out amount of bail that allow for be possible. Type of Online Processing Riordan Manufacturing leave behinding need to decide between real time asynchronous serveing and batch processing. Real-time asynchronous processing is relevant when the processing moldiness be performed immediately or when the results must lastly be communicated back to an online user.One of the problems with real-time processing is that real-time timers and events ar required they are expensive as the computer resources that are used to raise, maintain and touch events. An another(prenominal) problem with timer or even processes is that they create locking problems as they may contend with on-line processes for resources and for entrance fee the same data. Batch solutions are ideal for processing that is not real-time event based. Batch processes are data-centric and potty efficiently process large volumes of data off-line without affecting the communitys on-line form.Batch processing entrust allow business function to lean on a periodic or recurring basis or it tooshie operate over data that matches a given criteria. afterwards studying Riordan Manufacturings Inventory and Supply Chain processes, the recommendation is for the company to go with batch processing for replenishment of raw materials for the operations. With daily account of the materials used at the end of separately manufacturing run as the on-going method of inventory control, batch processing will work well. season real-time processing works well for online shopping, it is not the best prelude to take for this application.Access Privileges Normally it is not considered a good security risk to grant access to individuals/companies who are located outside of the normal company network and/or firewall. But in order to give a better integration of the database between Riordan Manufacturing and vendors/suppliers it is necessary to allow hold in access. Riordan shall touch on the types of privileges to grant to vendors. These privileges include (a) view, (b) insert, (c) modify, and (d) delete (logarithmical deletion single). Riordan shall also determine the type of data vendor should be able to access.The data should only relate to the materials that have been used in the daily manufacturing run materials that have been previously placed on order and the estimated projections of materials needed for the upcoming workweek. This will allow both Riordan Manufacturing and the suppliers to determine the present and short-term inv entory needs. Bandwidth broad(prenominal) speed access of the Internet has decreased in cost in recent years and the increased utility and the increased ease of use versus the cost of acquiring and maintaining the access has become more financially feasible.LTB and Associates recommend that Riordan acquire the appropriate bandwidth that will allow for the effective flow of instruction and which will support concurrent access of the company database. Security With the ever-growing threats that are present in the web-based global economy, there is an increased awareness of security. This includes both corporate and political terrorism as well as the inner lone user bent on mischief. LTB and Associates recommend that the administration plan should ensure that there are methods of data security implemented as information travels over the internet.An effective firewall should be implemented to deny access to unauthorized people. Data should be encrypted. Whenever possible, a Virtual Private meshing be craped between Riordan Manufacturing and the larger and more critical suppliers Database presidentship Plan To ensure the productivity, continuity, and process of the database for Riordan, proper bread and butter, database backup, and change commission procedures must be developed and implemented. The database must be backed up regularly in case the system needs to be restored due to data corruption or the loss of the data center due to vivid or man-made adventures.Database backups are also critical for interrogatory upgrades, fixes, and enhancements that will need to be migrated into return. Periodic maintenance is also a mention to database performance and continuity. Applying operating system patches and security updates to the servers that house the databases help cargo hold the software updated and the servers performing efficiently. Consistent re-indexing of the database deal help keep performance high as the database grows in size. Another ver y important part of administering a database is change management.Database upgrades, fixes, and enhancements must be tested and implemented in a manner that minimizes authorisation errors, disruption to users, and preserves an audit racetrack for troubleshooting and compliance issues. Database Backup Plan In order to minimize potential data loss and downtime, the database will be backed up each night and stored in a secure location on the network. Storing the backups on the network will help facilitate transferring the backup to the hazard recuperation site. Once the backup is created and stored on the network, a copy will be encrypted and transmitted to the disaster convalescence ite. The backup can and so be easily restored at the disaster recovery site as needed, or used in a development environment for testing upgrades, fixes, and enhancements. Database administrators will also have the ability to create backups as needed for testing or emergency purposes. Database backup s will be restored to the disaster recovery database at least bi-monthly to verify that the backups are generating correctly and that the disaster recovery-restore process is operative as it should. Maintenance Plan Once a month, the database servers will undergo scheduled maintenance.Operating system patches, security updates, and database application patches will be applied to the hardware housing the database in order to ensure the system is kept up to date. Database hardware will also undergo symptomatic checks to ensure allthing is working properly. At this time the database will also be re-indexed to preserve performance as the database grows. The patches, security updates, and database application patches will be applied to the development servers one week prior to implementation on the production server.Applying the maintenance related patches to the development system a week prior to implementation in the production system will allow time to monitor the development syste ms for any issues resulting from the patches and ensure the patches are synthetic rubber to install into production. For emergency maintenance issues such as hardware failures or power outages, the disaster recovery database will be restored from the a la mode(p) production backup and work should be closely coordinated with the server team up to ensure proper procedures are followed. Change Management The backbone to any administration plan is change management.Maintenance, database backups, upgrades, and other events must be guardedly tested, planned, and executed to minimize potential consequences including data corruption and downtime, and changes must be closely tracked to preserve the integrity of the database, maintain a log of changes for troubleshooting potential issues, and ensure proper testing and compliance controls are met. The database team will use Microsofts Visual Source Safe (VSS) as the main tool for version control. Patches, fix scripts, and any other rule th at applies to the databases will be stored in VSS and roper jurisprudence check in and check out procedures will be followed to ensure the proper code changes are migrated to the database. Only database administrators will have the ability to migrate changes to the databases. begeters can check out and modify code, but cannot implement any changes in the databases. All changes will be properly tested in a development database and signed off on by the appropriate parties. A network of IT and business approvers will be established for each business area (for example accounting, procurement, sales, etc. ) and will be responsible for subscribe off on changes that affect their particular areas.There will be at least one main approver and one backup approver that are subject matter experts for their respective business areas so that all areas utilizing the database will have a representative. Approvers will be the preferred testers, but other users may test changes as long as the appro vers review the test results prior to signing off on the test. Signoff for changes will be obtained via netmail using a template that details the change to be made, a tracking number for the change, and the location in VSS where the change is stored, so that the database administrators will be able to pull the change directly from VSS for implementation.Database administrators will not proceed with migration of a change until all appropriate approvers have responded in the affirmative. Disaster Recovery Plan (DRP) While preparing a disaster recovery plan (DRP), it is essential to think about the hardware, software and data that will be used to allow for an organization to continue operations in the event of a natural disaster or a disaster caused by human hands. In considering the idea of protection of the database, this plan will not only help preserve the companys investing but also secure the customers faith in Riordan.Some companies clear some 25% of their information technol ogy budget on disaster recovery plans. LTB and Associates recommends the implementation of a DRP. The cost of implantation and the subsequent maintenance versus the cost of a data loss is negligible in the meeting it would have. The first step in drafting a disaster recovery plan is conducting a thorough risk analysis of the database systems. Make a list all the possible threats to system operation and evaluate the likeliness of their occurrence.The threats can include electronic-based such as virus attacks or data deletions, deliberate or accidental and natural disasters, such as fire, flood, push or earthquake. Once the threats have been identified and ranked in likelihood of occurrence what can be done to minimize or square off the impact from these disasters. The more preventative actions we can establish in the extraction the better. It is better to take a proactive rather than a antiphonal approach in determining and documenting the DRP.The recovery procedure will be wri tten in a detailed plan defining the roles and responsibilities of the IT staff. defining how to compensate for the loss of various aspects of the network (databases, servers, communications links, etc. ) and pronounce who will arrange for these repairs and how the data recovery process will occur. communion Plan During a disaster situation, all parts of the communication plan should be cleared with a central location. All information should be reviewed by management before being released.LTB and Associates recommend that the following locomote be implemented. 1. Communication methods need to be established in advance. (Wireless or satellite telephone systems, email address, etc) 2. Develop templates for press releases, and include the scientific discipline sets of key employees, customer information, supplier information. Include maps of locations that may be exhausting to communicate in. Develop logs that can be used to track unveiling and outgoing communications. 3. Make s ure that these processes are easy to understand.4. Develop a contingency plan should the computer network where data is stored is damaged. Use text edition files and several copies in different storage devices and store this information in a remote server or on removable media which is then stored offsite. 5. Determine what is to be considered as privileged/proprietary information establish which levels of management and the key personnel to have access to the information and the approvals for accessing the information 6. Develop a set of detailed documents and instructions that can be shared with employees. . erect a set of technology based tools. 8. Develop a detailed training plan be sure to include all key personnel, top management and support personnel that can interface with customer and/or suppliers. 9. Develop relationships with News Service agencies. 10. Establish and train employees as observers to watch for individuals with microphones and notepads make sure they are aw are of the proper channels of communications. 11. Do plan periodic mock scenarios and drills of disasters in order to review the DRP.LTB and Associates recommends that the follow items be purchased, maintained, implemented, and stringently adhered to at every Riordan Manufacturing plant in the continental USA. taproom Plan An electronic manual. A printed hardcopy manual. Data and Software Backups Daily backups, local to each plant and stored offsite. periodical backup, to be performed system-wide by the Atlanta, Georgia plant and stored offsite. Storage area networks. puff Protectors and Power Supply Fault Switches. Anti Virus, Firewall and Security Software. Fire Prevention and Detection Smoke detectors and fire alarm systems. Fire extinguishers. Review and update insurance policies for all facilities and equipment. Disaster Recovery Process. In the event of a disaster occurring at any Riordan Manufacturing plant the following steps should be taken to restore the ope ration of the system to normal operation. The steps can apply to any and all sites. 1. Contact the proper level of management and notify disposed(p) personnel a. Determine if the equipment is functional and has suffered no damage. b. reconstruct or replace the equipment as needed per the situation.2. Retrieve the latest periodical backup from the Atlanta, Georgia server and/or facility. (Note if the Atlanta plant is the modify plant, retrieve the last weekly back up from the offsite storage facility) 3. rectify the database to the server. Perform a system check for proper operation. 4. Retrieve the latest daily backup from the offsite storage facility. 5. Restore the database to the server. Perform a system check for proper operation. 6. Retrieve and key in any pertinent data that was recorded on hardcopy sources from the affected plant and double check accuracy with personnel if possible.