The following information is in regards to a Product Lifecycle Management system being implemented into an organization for the Human Resource department.
With any implementation there are many factors that must be planned and prepared for before a successful integration can be assured. The following few pages will disclose the hardware and software; the testing plan; and the user documentation and planning strategy will be included.
Before one can implement a new system within a company it is important to understand the rules prior:
- “Proper planning
- Not having the right people on the team from the start
- Not setting priorities
- Not investing in training
- Importance of accurate data (Schiff, 2012)”
These are key rules for a successful project. When planning from moving to an old system to a new many would recommend just turning off the switch and launching the new system immediately. Before this should happen the employee must know how the new system will work, what it may look like, things to expect and of course, a back-up plan if the new system is not successful the day of launch.
Depending on the type of system some systems may need to be “turned off” and start with the new system immediately. This technique will need to be planned appropriately and ahead of time.
To begin, the PLM system that is being integrated will need the following hardware and software installation.
- Ensure .Net Framework version 4 is installed.
- If IIS is not enabled, manage server and add role for application server.
- In the IIS manager, right click on the Default Web Site and select Advanced Settings under Manage Web Site. Change application pool to ‘ASP.NET v4.0’.
- Implement the stored procedure with the triggers (out of SQL)
Software versions and/or builds:
- Java Development
- Tomcat (Apache)
- SQL Server
- PLM Server
When converting to the old system one will need to ensure that it does not disrupt current business. Many suggest that a new server be implemented and before turning of the old system to set up a date and make sure the participants or employees are fully aware of this change.
Scrub the data
The term “scrubbing the data” is “also called data cleansing, is the process of amending or removing data in a database that is incorrect, incomplete, improperly formatted, or duplicated. An organization in a data-intensive field like banking, insurance, retailing, telecommunications, or transportation might use a data scrubbing tool to systematically examine data for flaws by using rules, algorithms, and look-up tables” (Rouse, N.d.).
The new system must be cleaned. Data drops are usually part of conversion. It is a quick way to import history from the old system but it must have the new rules created on the history before importing to the new system.
Testing is most crucial within any new implementation. There are many steps to a successful implementation. Other than “educating, designing and developing”, “testing and ensuring validation” are key steps to positive feedback once the system is launched (Benefits, N.d.).
“The more testing the better, and agile development recognizes that testing is not a separate phase, but an integral part of software development, along with coding. Agile testing empowers all members of a cross-functional agile team to ensure delivering the product value expected by the customer at frequent iterations. Agile teams use a “whole-team” approach to elicit feedback from customers, collaborating with the development team to turn these responses into executable specifications that guide coding. Testing and coding are done incrementally and iteratively, building up each feature until it provides enough value to release to production” (Importance, N.d.). A good way to test the system is to get a group of employees to run as many scenario’s as possible which will then reside with the acceptance test if the testing phase is successful.
During the testing phase or the Acceptance testing phases one will find issues somewhere along the line. Take note of each test and label them accordingly. Giving a status would be a good indication of how the testing is being accomplished. Statuses of each test should be listed as: Not Ready, Ready for Review, Approved, or Implemented.
There are many ways to have the employees look at a new system as a benefit rather than a havoc (Benefits, N.d.). Training the employees, which we will call “train the trainer”, can benefit with any form of implementation.
Training manuals are a necessity for ensuring proper training is performed. “An employee training manual can serve many different purposes. As the name suggests, the primary purpose of training manuals is to train employees. However, training manuals offer additional benefits even long after the training is complete. For instance, a well written training manual not only equips an employee with excellent skills, but also serves as a reference tool and guide for other employees. Regardless of the training of individuals and groups, written documentation can be a much better guide to understanding various processes. Written handbooks ensure quality and consistency in training methods” (Silberman, 2014).
Overall, a system is just a system, right? There must be approval from top down and it must be enforced to be a successful launch. If the systems functions perfectly, it will fail if it is not enforced from the top down. Ensure that every employee is trained properly and fully understand how to use the new system. Unfortunately a system can fail because the employees refuse to use the unknown system. This would be worst case situation and actually should not exist with any new implementation, but unfortunately it happens more than one would think.