References to standards (e.g., ISA, Underwriters’ Laboratory, and National Electrical Code); and
• Appurtenances (e.g., mounting hardware, special tools, or calibration equipment).
The “execution” section (Part III) of the specification details the requirement for implementation, including field testing, quality control, and others. Before the owner accepts a new or modified process control system, the system or modifications should pass the following three performance tests consistent with the size of the project:
• Factory acceptance test (FAT),
• System availability test (SAT), and
• Site demonstration test.
The FAT demonstrates that the control system is built to the project’s requirements (including specifications), that the system is in accordance with the manufacturer’s shop drawings, and that the system is properly configured and ready for shipment to the job site. After field installation, instrumentation testing should be integrated to SAT, which typically duplicates FAT testing at the job site using installed devices to completely test control system hardware, software, wiring, and communications media.
Test criteria for these tests is developed by the design engineer, but the system integrator develops detailed test procedures for each control system because testing requirements may be unique based on the site and custom SCADA system. Testing is conducted by the system integrator and witnessed by the owner or design engineer. Instruments may be tested at the factory or in the field. Individual instruments (i.e., transmitters) and groups of devices (e.g., control panels) can be tested.
During startup of the process control system, the contractor may have to tune control loops and demonstrate that the instrument works properly. For some devices (e.g., magnetic flow meters, mass meters, specialized analytical instruments, emission monitoring systems, etc.), a trained representative of the instrument manufacturer should commission the equipment for the contractor to properly demonstrate operation.
Training specifications may require a minimum number of training hours and trainers’ resumés and require the contractor to submit a detailed outline for each course. These training courses should cover process control system hardware, software, and instrumentation.
Specifications should also require the contractor(s) to provide the following control system documentation:
• Corrected as-built drawings,
• Shop drawings,
• Panel drawings,
• Fiber-optic patch panel drawings,
• Loop drawings,
• Application program documentation,
• Hardware configuration documentation,
• Control system hardware and software,
• Control system interconnection drawings,
• Communications equipment hardware and software,
• Manufacturers’ data sheets for all instruments, and
• O&M manuals.
As part of final documentation, these documents should be furnished in a searchable, editable electronic format and in paper copies. Electronically formatted data can then be incorporated to the facility’s documentation or maintenance management systems. The type of documentation must be specified to enforce requirements for the contractor.
Specifications should also require the following types of schedules:
• Instrument lists (field and panel);
• Device nameplate or tag engraving;
• Reports (process and regulatory);
• Human–machine interface or OIT graphical screens;
• Programmable logic controllers’ I/O;
• Data register mapping;
• Historian data;
• Network configuration settings; and
• Device names.
2.5 MasterFormat 1995
The CSI has published a list of standardized numbers and titles for organizing bidding documents. According to CSI, this format has been in existence for more than 40 years. Use of a standardized document organization system allows owners, engineers, contractors, and others to find information in a predictable location.
2.6 MasterFormat 2004
The CSI has published a list of standardized numbers and titles for organizing bidding documents. According to CSI, MasterFormat is a living document; it was fully revised and reorganized in 2004 and updated in 2010. This format remains a standardized document organization system enabling owners, engineers, contractors, and others to find information in a predictable location. The increased number of sections allow for growth, flexibility, and additional detail.
2.7 Whole Building Design Guide
The Whole Building Design Guide was published as part of the National Institute of Building Sciences in 2012. Unified Facilities Guide Specifications (UFGS) is a joint effort of the U.S. Army Corps of Engineers, the Naval Facilities Engineering Command, the Air Force Civil Engineer Support Agency, the Air Force Center for Engineering and the Environment, and the National Aeronautics and Space Administration. The UFGS specifications are updated quarterly and are published at http://www.wbdg.org. Although UFGS is designed for use in specifying construction for military services, the content provides a template and technical information for developing project specifications for other applications.
3.0 REVISIONS TO TECHNICAL CONTENT
3.1 Notes to Specifiers
In addition to technical content of the specifications, notes to the specifier within the guide specifications should be revised to reflect updates to content or application from both successful and challenging projects.
3.2 Installation Lessons Learned
Specifications should be regularly reviewed and updated to address questions generated during bidding, construction, or changes in technology. Technical content should be reviewed before every signifcant project and at least every 3 years. Updates should include information and data accumulated during implementation of projects.
4.0 INSTRUMENT DATA SHEETS
An option to providing text-based specifications is to use instrument data sheets. These are form-based requirements that can provide more detail than text-based specifications in a format easily imported into a maintenance system. Data sheets can be paper-based, electronic, or both. Significant effort is required to properly complete data sheets. Properly completed data sheets can exist
