The Implementation Phase

Having agreed on suitable dates, I traveled to Arizona to the town where the plant was located. The entire team met me in the refinery office, where I initially met Susan and other members of the safety team. A contract was signed and I received the check on behalf of NOSA. The formal implementation training was to start the next day and continue for the next 2 weeks. 

Every day for 2 weeks I put students through the 1-day classes. Then I took them on an inspection of the workplace, after which we returned to the classroom to execute a mini audit of what we had seen and evaluate it against acceptable standards. They were flabbergasted by what they saw. They learned about structured safety systems and what physical work conditions should look like, and how management safety controls drive the safety system. 

---

The implementation phase represents the delivery of the training. Classroom, self-study or computer based training is typically suitable for knowledge related objectives. Hands on performance training, walkthrough or simulation is most appropriate for procedure tasks. 

Each of these parameters is specified in detail during the planning phase of the project. These specifications then form the basis for control during the implementation phase. 

The implementation phase is comprised of the actual outage duration. During this period, all of the tasks included in the scope of work are scheduled for completion. 

By this stage you will typically already have an idea of all of the above issues, since you will have had to advise the sponsors on them when vying for their support however, the implementation phase serves to finalize and consolidate initial ideas. What is more, this phase should involve all stakeholders as much as possible in order to create a scheme that wiU be supported and accepted. 

The implementation phase can be viewed as a period of actual closure operations, followed by facility closeout (postmortem). Here, too, there may be some overlap of the two activities. Finally, the facility site may undergo postclosure activities in accordance with agreed-upon regulatory requirements. 

The Implementation phase is treated in the ensuing chapters from the perspective of each of the levels at which a manager operates organization, group and self. At each of these levels there is a central dilemma that managers and project leaders continually need to resolve ... 

For all sorts of reasons, plans may not work out as intended. Moreover, there may have been uncertainty from the outset about the realism of planned activities and the deadlines set for them. Sometimes it is possible to plan only in outline before embarking on the implementation phase. 

Most of the efforts of the authors who contributed to this book were focused on presenting, in a clear and understandable way, different approaches and assumptions employed for modeling SOFC operations. In particular, the book intends to be as transparent as possible with regards to data and formulas used in the implementation phase. 

With the completion of the QA Manuals and training of personnel in QA practices, the laboratory proceeded into the implementation phase of the program. At DCLS, audits are conducted internally at the Section and Bureau levels, and externally by... 

Finally, in phase three, one finds that the laboratory has passed out of the Preparation Phase and is now in the Implementation Phase, which is the longest and in some ways the most difficult. It is during this period that the laboratory begins to operate under the new rules and it is when all members of the analytical team, regardless of their opinion of the GLPs, must come into conformance. It is the period of testing and modifying the processes everyone worked so hard to prepare. 

The most critical of these actions, in order both to generate the best ideas and to get them implemented, is ensuring the full participation of cross-functional resources on teams, e.g., manufacturing, maintenance, R D, and marketing. When all key areas are represented, buy-in and implementation questions can be addressed in a continuous and iterative manner. In addition, once an idea has made it through discussions within cross-functional teams it stands a much better chance of getting through the implementation phase. 

The implementation phase of the data collection process takes place in the field and at the laboratory where the SAP provisions are implemented. This phase consists of Task 3—Sampling and Field Data Collection, Task 4—Laboratory Analysis, and Task 5—Field and Laboratory QA/QC. In theory, if all sampling, analysis, and QA/ QC tasks of this phase are conducted to the requirements of the SAP, the collected data will be relevant and valid. In reality, most projects have variances from the requirements specified in the SAP, hence a need for the next phase of data collection, i.e. assessment. 

The distinction between the two definitions lies in the fact that due to unpredictable circumstances or errors in the implementation phase, some of the planned samples may not be collected and analyzed or some of the analytical parameters may be for some reason omitted. Based on two definitions of the total number of measurements, analytical completeness may be calculated in two different ways as shown in Equations 3a and 3b, Table 2.2. 

After the planning phase of the data collection process has been completed and the foundation of the data collection pyramid has been built, the project moves into its second phase, implementation. The implementation phase takes place in the field and at the laboratory. This chapter addresses the tasks of field implementation, such as Task 3—Sampling and Field Data Collection and Task 5—Field QA/QC, shown within the data collection pyramid in Figure 3.1. The main features of these field tasks are sampling procedures sample custody and tracking preservation techniques equipment decontamination field screening and record keeping. 

The second half of the implementation phase of the environmental chemical data collection process consists of Task 4—Laboratory Analysis and Task 5—Laboratory QA/QC. Arising from a foundation of project planning and following field sampling implementation as shown in Figure 4.1, these tasks transform the collected samples into chemical data. 

The importance of this exercise cannot be overemphasized. If the system contains incorrect informahon, there could be GxP compliance issues and, from a practical perspective, users quickly become disillusioned with systems if they cannot rely on the information they contain. Hence, it is important that the information is also maintained during the implementation phase to ensure that any documentation updated in the hardcopy system is also updated in the EDMS. 

Finally, by applying the appropriate indicators from the value driver trees mentioned in the previous section, management can lay the groundwork for comprehensive and practical monitoring of performance improvements during the implementation phase. 

During the implementation phase, the system shall be validated to make sure that it meets the expected requirements stated in the URS. Many literatures have described the LIMS validation. Validation is not an issue in this article. 

Structural testing is done in the development department and starts during the implementation phase. Code modules are checked individually by the programmers and may be formally inspected by peers, if appropriate. Modules are tested by programmers with specific test suites and then linked together into a system and tested as a whole for proper functionality to ensure that designs are correctly implemented and the specified requirements satisfied. 

Implementation phase In the implementation phase, processes and process modihcations are installed and integrated to the exishng system, commissioned, and put into operahon. All operators and workers are trained for the changes in the process and new processes. 

The final phase in the SDLC covers the implementation — that is, the systematic approach to effectively integrate the software into the process of an organization. Depending on the size of the software, the number of end-users, and the number of interfaces to other software systems, the implementation phase can be anywhere... 

---