Automation of Water Resource Recovery Facilities. Water Environment Federation

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 and be useful for the life of the instrument or project. Data contained within the data sheet can provide useful information for a maintenance database.

5.0 CONSTRUCTION SPECIFICATIONS INSTITUTE

      5.1 Performance-Based Specifications

      Performance specifications can be used when the specifier allows the bidder to use greater flexibility in proposing equipment or methods to meet project requirements. Performance specifications are advantageous when technology changes.

5.2 Descriptive Specifications

      Descriptive specifications can be used by the specifier when bidder requirements are restricted with respect to equipment or methods for technical content or project requirements.

6.0 OWNER-DEVELOPED SPECIFICATIONS

      Project specifications must be reviewed and understood by the specifier before being issued for a project. To improve standardization on a site or through an organization, specifications can be developed by the organization that identifies equipment standards. Both technical and administrative specifications prepared independent of the project and offered for the project should be reviewed and edited to confirm that they are coordinated within the project manual. Another method for an organization to establish equipment standards without the constraints of a specification is to issue expected standards of automation, sometimes referred to as automation standards. Automation standards do not need to follow an established format and the content most likely will affect multiple specification sections. When an automation standard is issued, it is reasonable to expect that those standards will be incorporated to project specifications in the appropriate section. Incorporation of automation standards by reference is not prudent because conflicting requirements may be issued. Regardless, the specifier must verify that conflicting specifications are not issued.

7.0 COORDINATION WITH OTHER DISCIPLINES

      Coordination of specifications for process control systems with project specifications for other disciplines, including process equipment, is essential. For example, implementation of system-wide uniformity in requirements for packaged systems (pumps, screens, centrifuges, and drives) requires either specific reference to instrumentation requirements or repeating them in equipment specifications. To reduce the risk of errors when specifying devices in more than one location, it is strongly recommended that requirements be written in one place only. As such, the reader is encouraged to include text within the other discipline section to meet the requirements of instrumentation specification. While simplifying paperwork for the contractor, listing requirements for devices and control panel details in the equipment specification requires careful replication to ensure device matching.

8.0 REFERENCES

      Construction Specifications Institute (2005) The Project Resource Manual; CSI Manual of Practice, 5th ed.; Construction Specifications Institute: Alexandria, Virginia.

      Instrumentation, Systems, and Automation Society (1991) Instrument Loop Diagrams; Standard ANSI/ISA-S5.4; International Society of Automation: Research Triangle Park, North Carolina.

      Instrumentation, Systems, and Automation Society (1981) Specification Forms for Process Measurement and Control Instruments, Primary Elements, and Control Valves; Standard ISA-S20; International Society of Automation: Research Triangle Park, North Carolina.

9.0 SUGGESTED READINGS

      American Water Works Association; American Society of Civil Engineers (1990) Water Treatment Plant Design, 3rd ed.; McGraw-Hill: New York.

      American Water Works Association