Q. Why were you inspired/motivated to write this book?

A. There are many books and other resources available on engineering project management. However, there are few available on control systems engineering project management, and none available—that I am aware of—on process analyzer engineering project management. By writing this book, I hope to ease the engineering and design burden for new and experienced engineers who work on process analyzers.

Q. How would you describe the book’s core value to readers? Why and how would they benefit by reading it?

A. In my experience, process analyzers are the least understood of the petrochemical and refining disciplines and sub-disciplines. This book presents an opportunity for analyzer engineers and engineers in other areas of project engineering to understand each other better and produce higher-quality new and revamped plants and operating units where process analyzers are needed.

Q. What is the most compelling challenge that the book addresses?

A. Quality. Of the three corners of project management—cost, schedule and quality—quality is the most difficult to measure and control and, as a result, the most often overlooked. Though quality can seldom be quantified, this book should help engineers identify situations that have the most impact on analyzer engineering quality. 

Q. What makes this book different than other books on the subject? What differentiates it?

A. The first difference is the emphasis on quality and ways to improve and ensure high-quality projects within the limits of budget and schedule. Secondly, the book includes useful photographs and informative engineering drawings of completed analyzer engineering projects. And thirdly, the book provides a complete illustration of all the steps within a realistic project—beginning with project conception to project turnover.

Q. Are there any specific sections/aspects of the book do you feel are the most compelling to highlight in the press release?

A. Several chapters, in fact, come to mind. Chapter 1, on safety and ethics, is by far the most important chapter; it delineates the professional engineer’s first obligations to the public. It includes: key excerpts from NFPA standards; an excerpt from state engineering laws and rules; and complete codes of ethics from well-known engineering societies. There is also a link to the website of a public tragedy in 1937 that could have been prevented had engineering safety principles been applied. Along with Chapter 1, Chapter 3 on project risks and quality is key to maintaining budget, schedule and quality.

Throughout the book, I encourage readers and users to add their own experiences and ideas to those in the book, and to change the tables, templates and lists to fit their own situations. In addition, Chapter 4 on project scope and Chapter 5 on data sheet preparation vitally important because a successful project begins with adequate and accurate documentation; it’s always less costly to improve documentation “up front” than to reorder and rework later in a project. I illustrate how to use the best process analyzer data sheets and formats.

Q. Do you have any other comments to make about the book?

A. Much of the book is written in a “how to” style to give process analyzer engineers a starting point for meaningful project work on process analyzer projects. Though I encourage readers to customize the information to fit their own situations, using these templates to get started will at least help members of the analyzer engineering community to begin writing out the required documentation. Furthermore, the ideas in this book can be rewritten by appropriate subject matter experts to fit other areas of automation and instrumentation beyond analyzers.