Administration/013 Administration Sequence of Operation.pdf

Return to Procedures Main Menu

Index: Administration

Subject: (13) Sequence of Operation

Date: August 30, 2004

Revised November 5, 2009

Revised October 15, 2013

A sequence of operation will be included with every submittal.

If Sales provides a sequence of operation from the customer, it must be evaluated by Engineering to determine if it is complete and accurate in describing the operation of the unit that we are providing. If the provided sequence is acceptable, a copy of the sequence will be included in the submittal. A cover page (H:\EngMstr\SEQ\customersequence.doc) to the customer’s sequence of operation citing the specification section and/or drawing number where the sequence can be found in the contract documents shall be provided. The cover page will be saved in the FO ( J:) drive ”Written Specs-Sequence” folderas FOFO##_SEQ.doc.If the sequence provided is not accurate, the project engineer will create a sequence of operation for the unit. If the sequence provided is accurate, but does not fully describe all required operations, the project engineer will create a supplement to the sequence provided to address all missing items of concern. The project engineer should strive to meet the intent of the customer’s sequence as much as possible based on the unit that we have designed. Sales should be notified via e-mail that the sequence of operation that was provided cannot be used so that he can get approval of the sequence that we are submitting. For complex projects, the project engineer will review the sequence of operation with the controls engineer for the project prior to release of the sequence of operation to insure that the sequence of operation is complete and accurate, and the control system has been designed and programmed to meet the intended sequence of operation.

 

If no sequence of operation is provided by Sales, Engineering will create a sequence of operation based upon the type of unit and specific options that are called out on the factory order, such as night setback, morning warm-up, etc. For special application units that such as 100% O.A. units or units for manufacturing or process environments, Sales must provide information to Engineering describing the customer’s intended operation of the unit from which the project engineer will develop a sequence of operation. In rare cases where absolutely no information is available to generate a sequence of operation and the controls are being provided by others, a generic “controls by others” sequence (H:\EngMstr\SEQ\controlsbyotherssequence.doc) shall be provided.

 

All sequences of operation should have a title so that it can be associated with a specific job, project factory order number, unit designation for multiple unit projects, and the date that the document is created. The sequence of operation as minimum should include: type of unit, description of major components, occupied/unoccupied mode of operation, cooling mode of operation, heating mode of operation, economizer mode of operation, and initial set points. Sequence of operationwill be saved in the FO ( J:) drive “Written Specs-Sequence” folder as FOFO##_SEQ.doc, where FOFO represents the four-digit factory order and ## represents a sequence number where multiple sequences as required (always start with “01”). Any revisions to the original sequence of operation shall have a revised date and the previous date shall not be overwritten.