The Apparatus Architect: Part 5

May 1, 2001
Tom Shand and Michael Wilbur discuss the process of gathering technical information to create the apparatus specifications.

Previous installments in this series have reviewed various concepts of how to evaluate your fire department's apparatus needs, how to initiate the apparatus committee and several methods for gathering technical information. This article will discuss the different styles of apparatus specifications and how to begin the process of putting all of the committee's ideas down on paper.

Developing and writing apparatus specifications can be a daunting task for many fire departments. The specifications are filled with dimensions, model numbers and verbiage that may be completely foreign to you. Reading an entire specification may seem like blank verse and leave you more confused than when you started.

You are not alone. Since most of us were not gifted to be technical specification writers, there are several methods that you can employ to get your committee off to the right start.

When your committee was collecting technical information, you probably obtained a set of specifications from another fire department or perhaps one of the apparatus manufacturers that you contacted. These documents can serve as an example of how a complete set of specifications may appear. It is important to recognize that there are several styles of apparatus specifications that can be used.

First is the manufacturer's or design style of specification. This document generally describes all of the components that are used in the construction of the vehicle, including most of the standard designs that are used by that particular manufacturer.

While this provides for a complete piece of equipment, this type of specification requires that other prospective bidders either take exception to the specification for a particular feature or change their design to meet your requirements. The balance needed here is to weigh the importance of a particular design that will meet the needs of your department vs. the "no exception" requirement for a design that is offered by only one manufacturer.

An example here would be to specify that: "The crosslays shall be no more than 64 inches from the ground to the bottom of the crosslay bed when the apparatus is fully loaded." This is a performance requirement that provides an opportunity for any manufacturer to design its apparatus to meet your need. Contrast this with: "The manufacturer shall provide for Brand 'A' heater which shall have an output of 55,000 BTU with overhead backlighted controls." This is too specific in that this make and model of heater is used as standard by only one manufacturer.

When you specify the make and model of the engine, transmission or tires, these can be met by any builder as it will attempt to meet your requirements in these areas. Remember that anytime you deviate from someone's standard, this impacts the price of the apparatus and that making the specifications too precise will preclude some manufacturers from bidding.

The second type of apparatus specification is the performance document, in which the fire department determines the minimum requirements for the apparatus. This lets the manufacturer offer its standard designs in response. An example would be the department requesting a 1,250-gpm single-stage fire pump. Here, each builder could offer its standard fire pump installation and components that meets this requirement. One of the problems here is that the fire department may not get everything it wants from each of the bidders, and there is little ability to compare from vendor to vendor exactly what is being offered to the department.

Another version is the open specification, in which the department can list each major component to insure that the bidders will all be bidding on the same configuration. Using this style of outline specification lets the committee identify each and every component on the apparatus without going into the detail of how the component will be installed on the apparatus.

There are dangers, however, when apparatus committees dictate specific components. If a specific component does not work, it can be argued that your committee specified it and ordered it, so now you own it. If you have performance-based specifications and the apparatus manufacturer supplies a component that does not work, the manufacturer owns the problem, not you. The more responsibility and liability the manufacturer takes on and the less responsibility and liability the apparatus committee takes on the better off the fire department will be.

The most realistic style of specification provides for some design criteria together with performance requirements for acceleration, braking and compartment design. In this manner, the apparatus committee can take advantage of each manufacturer's experience while maximizing the performance of the apparatus without paying for unwanted components or frivolous designs. The National Fire Protection Association (NFPA) 1901 standard has an excellent questionnaire in the appendix of the document that takes you through all of various components on a piece of apparatus. This document can serve as an outline for your specification and should be reviewed by the apparatus committee before the specification development process begins.

The third style of apparatus documents that may be used are request for proposal (RFP) specifications. These are much less detailed than a design specification. RFPs detail the manner in which the fire department will evaluate each proposal and how the department will determine the successful bidder. These specifications can be more difficult to write and to evaluate unless the committee has an extensive knowledge of manufacturing designs and component models. Overall, this type of specification lets each bidder offer compliant apparatus using its own construction methods while showing some innovative solutions to meet the department's needs.

Each of these styles of specifications offers advantages to the department, and with the advice of an apparatus architect the committee may be able to decide which specification will best meet its needs. Fire departments that operate large fleets typically have standard specifications for their apparatus, which are frequently updated to keep up with new components and model numbers.

Writing Thorough Specifications

While it is generally not a good idea to use a manufacturer's specification for a bid document, it is also not advisable to write your own specification by "cutting and pasting" different sections from various specifications. Unless your committee has the technical resources to evaluate each bidder's response, a specification that has a "little bit of everything" generally does not provide for a well-designed apparatus. By following the outline of a good, thorough specification the committee will insure that each of the bidders will have a clear idea of the department's requirements.

In this regard, do not use words in the specification such as "heavy duty," "best apparatus industry practices" and "for the intended use." These words mean little and do not convey exactly what the fire department wants. For example, if the committee desires a particular flow through a rear discharge, asking for "heavy-duty full-flow three-inch piping" means what to you? Specifying a three-inch rear discharge with the capability of flowing 500 gpm with a maximum friction loss of 15 psi at the outlet defines exactly what you want the performance level to be on the apparatus.

Writing apparatus specifications is a time-consuming job that requires patience and the ability to logically develop all of the ideas and concepts that the committee has reviewed into a written document. The end result of the specification development and bidding process is the award of the contract to the successful bidder.

The next installment of "The Apparatus Architect" will discuss aspects of the bid review and evaluation process.

Tom Shand, a Firehouse

Voice Your Opinion!

To join the conversation, and become an exclusive member of Firehouse, create an account today!