{"id":1022,"date":"2026-07-19T09:00:00","date_gmt":"2026-07-19T01:00:00","guid":{"rendered":"https:\/\/borrapumps.com\/blog\/jockey-pump-sensing-line-diagram\/"},"modified":"2026-07-19T09:00:00","modified_gmt":"2026-07-19T01:00:00","slug":"jockey-pump-sensing-line-diagram","status":"publish","type":"post","link":"https:\/\/borrapumps.com\/ru\/blog\/jockey-pump-sensing-line-diagram\/","title":{"rendered":"Jockey Pump Sensing Line: Drawing and Review Checks"},"content":{"rendered":"
\n

Direct Answer<\/h2>\n

A jockey pump sensing line tells the controller what system pressure it is monitoring.<\/strong> This guide helps contractors and project teams review a drawing or test plan without treating a generic article as an approval document.<\/p>\n

\"BORRAPUMP<\/p>\n

1. Start With the Project Drawing<\/h2>\n

Use the approved project drawing to identify water source, main fire pump, jockey branch, controller, valves, and test path. A supplier layout defines package scope; it does not replace the engineer’s system drawing.<\/p>\n\n\n\n\n\n\n\n
Review item<\/th>\nWhat to confirm<\/th>\n<\/tr>\n<\/thead>\n
Pressure reference<\/td>\nThe intended system point is clear.<\/td>\n<\/tr>\n
Controller input<\/td>\nSignal matches the project sequence.<\/td>\n<\/tr>\n
Isolation and test access<\/td>\nMaintenance path is defined.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

2. Check the Main and Jockey Duties<\/h2>\n

The main pump serves required fire-flow duty. The jockey pump maintains pressure against small losses and should not be treated as the main fire-flow machine.<\/p>\n

\"BORRAPUMP<\/p>\n

3. Review Controller Signals<\/h2>\n

Verify the pressure reference, controller connection, and intended start sequence against the project documents. Exact setpoints are project-specific and must not be inferred from a generic drawing.<\/p>\n\n\n\n\n\n\n\n
Signal<\/th>\nReview boundary<\/th>\n<\/tr>\n<\/thead>\n
Minor pressure decay<\/td>\nJockey response is reviewed first.<\/td>\n<\/tr>\n
Continued pressure drop<\/td>\nMain fire-pump sequence follows project documents.<\/td>\n<\/tr>\n
Test condition<\/td>\nUse documented procedure and records.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

4. Confirm Test and Drain Paths<\/h2>\n

The layout should show test points, drain paths, gauges, and isolation needed for the project procedure. Do not omit site safety and authority requirements.<\/p>\n

5. Review Package Supply Scope<\/h2>\n

List supplied pumps, drivers, controllers, valves, instruments, documents, and field connections. This avoids treating a package quotation as a complete site installation.<\/p>\n

\"BORRAPUMP<\/p>\n

6. RFQ and Documentation Checklist<\/h2>\n\n\n\n\n\n\n\n\n
Information<\/th>\nPurpose<\/th>\n<\/tr>\n<\/thead>\n
Required flow and pressure<\/td>\nDefines fire-pump duty.<\/td>\n<\/tr>\n
Water source<\/td>\nDefines suction interface.<\/td>\n<\/tr>\n
Controller requirement<\/td>\nDefines signals and scope.<\/td>\n<\/tr>\n
Requested documents<\/td>\nDefines commercial boundary.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

For fire pump package discussion, send verified project data through contact Borra<\/a>.<\/p>\n

7. Fit Boundary<\/h2>\n

This guide does not certify a fire-protection system or claim UL, FM, NFPA, or local approval. Final acceptance requires the applicable project documents, authorities, and verified product evidence.<\/p>\n

FAQ<\/h2>\n

Can a supplier drawing replace the engineer drawing?<\/h3>\n

No. It explains package scope but not the accepted project system.<\/p>\n

What does a jockey pump sensing line do?<\/h3>\n

It provides the controller with the pressure reference for its maintenance duty.<\/p>\n

What should testing records include?<\/h3>\n

Use the project procedure, controller documentation, and required authority records.<\/p>\n

Is the jockey pump the main fire-flow pump?<\/h3>\n

No. It maintains pressure for small losses.<\/p>\n

Can this guide approve a package?<\/h3>\n

No. Approval requires project-specific review.<\/p>\n

What should be sent for quotation?<\/h3>\n

Send flow, pressure, source, driver, controller, connections, documents, and destination.<\/p>\n

References<\/h2>\n