|
|
|
Course Category
|
|
|
|
Course Schedule
|
|
|
|
|
|
|
 |
|
Documentation Services
|
 |
SYSTEM DESCRIPTIONS developed by HPC are "Reader-Friendly" documents that describe the function and operation of the particular systems. A typical system description is outlined as follows:
- Objectives (used when the System Description is to be used as a learning tool in addition to being a reference document)
- System Purpose
- System Overview
- Major Components and/or Sub-Systems
- Instrument & Controls
- System Operation
- Operational Alarms
- References
OPERATION PROCEDURES are developed by HPC and include detailed step-by-step procedures on how to place a particular piece of equipment (or system) into service. Procedures usually include normal and emergency shutdown procedures as well. Some of our clients have desired these procedures to be used a learning tool. In this case, we authored explanations as to what a particular step in a procedure accomplished and why this was important.
PREVENTIVE MAINTENANCE PROCEDURES includes step-by-step procedures to properly care for equipment and/or systems as recommended by the OEM. These procedures often are very similar to what is provided in the OEM manual, but there is typically value-added in the sense that tools are described, only those steps applicable to the model in question are discussed, and consequences of not maintaining the equipment is emphasized.
LOOP DIAGRAMS are E&I type schematics that follow a signal from its origination to the final control instrument. For example, a pressure switch in the field results in a unit trip. The pressure switch as a device name, it is wired to a local junction box, there is usually a wire-tag that describes its connection to the terminal board in the control system, from the terminal board this signal may be digitized and stored in RAM, now it has a "signal name". Wouldn't it be nice to have identified, on one piece of paper, all the elements of this signal? This is what we accomplish on a loop diagram.
ALARM RESPONSE MANUALS are created for the benefit of operational personnel. It takes any alarm that might occur, describes the consequences of the alarm (in other words, what might be damaged and how serious it might be), and describes what action the operator should take in response. Should we get on the telephone and call someone, should we "trip" the unit, should it be unloaded, or what? If correlating data might be useful, this information is included as well.
TROUBLESHOOTING GUIDES takes the alarm response manual to the next level. In other words staff personnel must know determine what is the "root-cause" of the alarm and determine corrective actions. This may mean to replace a faulty pressure switch, to replace a "plugged" filter, to commence a clean cycle on some system, or to repair (replace) a circuit card.
POWER-DOC is essentially any one of the above described documents that has been organized as an electronic learning tool (in addition to being a reference document). We take existing system descriptions, for example, and put them in to an Acrobat Reader format (a .PDF file - a play on words for us is to make it into a Power-Doc file). Anyone can do this. What we do next is special. We wrap this PDF file with educational software such that the PDF is driven by an external software package that has objectives, examinations, and job-performance-measures (recommended on-the-job training tasks).
An example power-doc can be downloaded by clicking on the icon below. Caution is recommended, however, this file is about 10-MB. An alternative approach is to call us and we'll send you a sample CD. This power-doc is a complete system description, captured within an educational package, and presented accordingly. The system is your "coffee pot". Again, it is intended to be an example.
|
|
|
|
