Book Image

Operator Training Simulator Handbook

By : Joseph Philip
Book Image

Operator Training Simulator Handbook

By: Joseph Philip

Overview of this book

Operator training simulators in the process industry have been around since the 1970s, but you may not find a book that documents the development of these systems and the standard best practices. The Operator Training Simulator Handbook covers best practices for OTS engineering and OTS training development and delivery, starting from the basic the jargon and the different types of OTS systems. It will take you through the best approaches to project specification as well as building, maintenance, planning, and delivering these systems by sharing real-life experiences and dos and don’ts. As you advance, you'll uncover the various challenges in the planning and delivery of operator training models and understand how to address those by working through real-world projects. This book helps in specifying the best fit for purpose, choosing a cost-effective system when acquiring an OTS. You'll also learn how you can turn your OTS projects into digital twins before finally learning all about documentation in a typical OTS project, covering the sample structure that you can use as a starting point in your projects. By the end of the book, you'll have learned best practices for developing operator training simulator systems and have a reference guide to overcome common challenges.
Table of Contents (11 chapters)
1
Section 1: Introduction, Definitions, and Classifications
3
Section 2: Best Practices for the Development of OTS Systems
6
Section 3: OTS' Future, Training Model, and Reference Documents

Chapter 6: OTS Sample Documentation

One of the challenging issues relating to OTS projects is their documentation. In many projects, I have seen that documentation becomes less of a priority as the pressure grows on engineering tasks. Drawing up the documentation after engineering tasks had been carried out was not unusual when I first started working on OTS projects in the late 1980s. In certain projects, documentation was only drawn up once the OTS project had been delivered.

Documenting the OTS project will help in delivering a good project, meeting expectations, and identifying issues early enough so that they can be resolved before it becomes a question of fire-fighting. Does this ring a bell?

In the next section of this chapter, we will go over what documents are required for the V-model and see how this can help in project delivery.

In later sections of this chapter, we will provide a template for every document on the OTS project that OTS suppliers and users can use...