Flagship Wharf’s 12 batter-pile encasements have conflicting bid references

Flagship Wharf’s bid form lists 12 EA batter encasements as 03 31 30-04; the technical payment list uses 03 31 30-09. Keep both references pending clarification.

Guide6 min read

Published

Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.

Book a demo
On this page
  1. Keep the two printed references visible
  2. Count repair locations without inventing jacket quantities
  3. Compare the jacket method before comparing the rate
  4. Allocate the included work to the EA offers
  5. Use the clarification window to settle the reference
  6. Public source documents
  7. How we built the jacket comparison in Piper

Flagship Wharf’s Add Alternate 2 lists 12 EA batter pipe encasements under reference 03 31 30-04, but the technical payment list identifies batter encasements as 03 31 30-09. There, 03 31 30-04 instead means bulkhead concrete façade, measured in cubic yards. Preserve both source rows and seek formal clarification before mapping an offer into the bid form. IFB, PDF page 31; technical payment list, PDF page 60.

This source-linked bid and jacket-scope review was prepared in Piper, the AI operating system for preconstruction, using public project documents.

The discrepancy does not authorize a change to the owner’s bid form. Check the jacket materials, placement method and each-unit inclusions alongside the reference question.

This analysis uses the November 16, 2026 initial issue for the Boston Redevelopment Authority/BPDA project in the Charlestown Navy Yard, with an owner-page observation on November 17. It does not establish that no later addendum exists. The owner procurement page is the starting point for a fresh status check.

Keep the two printed references visible

The relevant bid row is Item 3, Add Alternate Bid 2, row 6. Read it against the technical payment list before normalizing codes in an estimate, quote comparison or BOQ import.

Reviewed sourcePrinted referenceDescriptionUnit or quantity
IFB PDF page 31, printed page 2803 31 30-04Batter Pipe Encasements, Add Alternate 2 row 6Estimated 12 EA
Technical specifications PDF page 60, printed page 1703 31 30-09Batter Pipe Encasements, Add Alt 2EA
Technical specifications PDF page 60, printed page 1703 31 30-04Bulkhead Concrete FaçadeCY

Sources: IFB bid form, PDF page 31 and Section 03 31 30 payment items, PDF page 60. These are public planroom copies of the issued documents; this review has not established byte-for-byte equivalence with every owner-hosted copy.

A code-only join could associate the batter encasement offer with a façade concrete row in a different unit. The crosswalk exposes that possibility. It does not show that any bidder made that mistake, that the work quantity changed or that compensation should be adjusted.

For the bid review, retain the original form reference, description, quantity and unit in separate fields. Record the technical reference beside them as an unresolved comparison. Ask for an interpretation through the prescribed process; do not silently replace “04” with “09” or convert the owner's 12 EA to CY.

Count repair locations without inventing jacket quantities

The reviewed S-105 Add Alternate 2 plan, PDF page 20, contains 32 filled pile-to-be-repaired markers across its two nonoverlapping views: 9 in View A and 23 in View B. That total reconciles with the bid form's estimated 20 plumb plus 12 batter encasements.

The count is useful as a completeness check. It does not independently establish which markers comprise the 20/12 type split, jacket lengths, grout volume or final payable quantities. The IFB expressly states that estimated quantities are not guaranteed and that final unit-price payment is based on actual quantities determined under the contract. See PDF pages 31–32.

Actual repair lengths require field information. Section 31 62 24 requires recording the mudline at each pile to the nearest tenth of a foot against Mean Low Water datum, with repair limits from the underside of the concrete beams to two feet below mudline. Submit the elevations and repair limits for Engineer review and approval before repairs. The requirements appear on technical PDF page 100.

Compare the jacket method before comparing the rate

A general concrete offer does not, by itself, establish coverage of this pile-jacket scope. The jacket specification makes several decisions explicit.

Check the actual performing crew. The contractor performing the repairs needs five similar projects in the preceding five years. The foreman and lead diver must each have worked on at least two of those projects. A company résumé alone leaves part of the qualification untested. Section 31 62 24, PDF pages 96–97.

Review the grout formulation, not only its compressive strength. The cementitious grout must be nonshrink, nonmetallic, contain no chlorides, be formulated for underwater placement and meet the specified criteria. Fly ash and slag are prohibited in this mix. A nominal 5,000-psi material does not establish compliance with the remaining requirements. See the jacket product requirements on PDF page 98.

Carry the installation sequence. The bottom epoxy seal must fully cure before grout pumping. Grout is injected from the bottom; tremie placement is prohibited for this jacket repair. The jacket and support devices must remain in place for 48 hours after repair concrete placement. The grout placement is one uninterrupted operation, with containment requirements protecting the marine habitat. See PDF pages 100–101.

These are project-specific jacket provisions. They should not be generalized into a prohibition on tremie placement or slag-bearing concrete for every marine project or every concrete component at Flagship Wharf.

Allocate the included work to the EA offers

Section 03 31 30 makes the plumb and batter encasement EACH rates full compensation for the associated work, including the specified preparation, testing, transportation, survey, supports, reinforcement, grouts, epoxy, curing and incidentals. Section 31 62 24 provides no separate measurement or payment for its jacket work. Read the encasement payment language on PDF page 60 and the jacket payment provision on PDF page 101.

The RFQ can ask specialists to identify who carries each requirement without creating new owner pay items. For example, an offer may include jacket installation while excluding the mudline survey, testing or temporary support work. Those exclusions need an explicit allocation in the estimate before carrying the EA rate. This is the same principle used in scope-based bid leveling: compare each offer with the required work and resolve the differences before selecting a carry.

No supplier responses were obtained for this analysis. The result is a source-filled review basis, not an approved product, qualified installer or completed quotation comparison.

Use the clarification window to settle the reference

The reviewed IFB schedules general bidder questions for December 8, 2026, responses by December 15, and general bids for January 7, 2027 at noon. It states that answers are issued by addendum and that bidders may not rely on other explanations as a substitute. See the procurement instructions on PDF pages 9–10. Recheck the current owner notice and addenda before relying on these initial-issue dates or the discrepancy.

The useful next step is a narrow prebid clarification that reproduces both references and asks how the batter encasement line should be reconciled. Keep the original 12-EA bid row intact while that question remains open. Pair the resulting interpretation with the jacket method and included-work review so the reference, technical scope and price stay connected.

Public source documents

The issued documents below are publicly linked from Northern Construction’s construction planroom. These are public planroom copies of the BRA/BPDA documents, not private contractor bids or customer-supplied files.

The project facts and requirements are cited beside the relevant claims above. Calculated quantities, scenario dates and comparisons are identified as analysis. No customer files were used as factual source material.

How we built the jacket comparison in Piper

In Piper, we prepared a source-filled jacket requirement matrix, an editable comparison and a drawing-marker count for this public package. The review keeps the conflicting bid references beside the required materials, placement method, qualifications and included work. Vendor response fields remain open until actual offers arrive.

Piper is the AI operating system for preconstruction. It connects scope generation, bid leveling and final bid review around the same project understanding. For the jacket package, the next step is to compare each offer with the documented requirements, allocate exclusions and retain the reference question for formal clarification before carrying the price. The engineer's interpretation and the estimator's commitment remain separate decisions.

ShareLinkedInX

Related reading

Piper removes manual review from the critical path and brings project data, company knowledge, and expert checks into every preconstruction decision and workflow

See Piper on your project

Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.