Data Center at Bell Works: Claims, Filings, and the Agreement

Note on acreage: confirm the exact size of the newly subdivided lot from the subdivision plat in the filed site plans before citing a figure in testimony. The legal point does not depend on the number: any new lot sized to hold parking, driveways, stormwater basins, and site improvements is by definition larger than the ~1.24-acre building footprint the Plan names.

The building itself was almost certainly sized to mirror the existing structure — that part lines up cleanly, and it's worth naming since it's the applicant's best argument. But "the general footprint of the existing maintenance building" describes the area the use is confined to, not just a roofline a new building happens to match. Parking, driveways, stormwater basins, and buffers are being carved out of a new lot several times that area — whatever its final acreage turns out to be on the plat.

"The data center will be supported by 34 parking spaces. In accordance with the Alcatel-Lucent Redevelopment Plan, the Data Center requires that 1 parking space per 1,500 square feet be provided. Accordingly, the Ordinance requires that 72 parking spaces be provided. As noted, 34 spaces will be available." Traffic Assessment, "Parking" section, p. 7 — the applicant's own report

A 53% shortfall against the Plan's own numeric standard (§V.B.2.c). The applicant's justification — low employee density, citing ITE data — may be reasonable on the merits, but it's still a deviation from a written standard, and needs a formal, on-the-record variance.

Three related but distinct names — the original signer, the current owner of record, and the letter's corporate signature — appear across this file. Worth asking directly whether Township consent was obtained for whatever restructuring produced this chain, and whether the current parties have formally assumed the 2014 Agreement's obligations in writing.

• Zoning schedule (bulk data: setbacks, coverage, height, FAR) — annotated "will provide as condition of approval," not submitted with the application.
• Easements, covenants, restrictions — annotated "condition of approval" rather than provided now.
• Water and sewer will-serve letters — the EIS states twice that "a formal will-serve letter is not yet available," despite the Township's checklist requiring current will-serve letters at filing.

The checklist item-to-note mapping comes from a scanned table; the two "condition of approval" annotations most plausibly attach to the zoning schedule and easements items based on document position — confirm against the original PDF. The missing will-serve letters are confirmed by clear prose in the EIS and are not in question.

This matters directly: the exact bulk data that would let anyone check this proposal against the underlying OL-1 zoning standard isn't in the record yet.

Holmdel's Noise Ordinance (Ord. No. 97-31, codified at §3-1) sets specific, enforceable outdoor sound limits at the property line of any residential receiving property:

Continuous mechanical noise from cooling equipment and transformers at data-center-scale facilities commonly runs in the 45–65 dB range at the property line — meaning ordinary 24/7 operation, not even generator testing, can land at or above Holmdel's 50 dB nighttime residential limit depending on distance and equipment. The open letter's claim that noise "will remain below state limits" is a specific, checkable assertion against these exact numbers — and nothing in the filed EIS shows the modeling that would support it. Given the architectural plans' own aerial base map confirms homes directly adjacent to the site (Finding 12), this is not a hypothetical concern.

Two more provisions worth knowing:

• Construction and demolition noise is exempt from these decibel limits entirely (§3-1.6.a.2) — only restricted by hours (no work before 7 a.m. or after 6 p.m. weekdays, none before 9 a.m. or after 6 p.m. weekends). The demolition of two buildings (Finding "Letter" claim #2) can lawfully be loud, with no dB cap, provided it stays inside those hours.
• Commercial/industrial power equipment is barred within 250 feet of a residential property line during evening/overnight hours (§3-1.6.b.2). Worth checking exactly how close the generator yard and mechanical equipment sit to the nearest home.

This is now the strongest concrete evidence-gap in the file: a specific, numbered legal standard exists, the applicant's own marketing claims compliance with it, and nothing filed with the Planning Board demonstrates that compliance.

The Master Plan carries two disclaimers, printed in red, in its own assumptions box:

"1. AREA FOR STORM WATER MANAGEMENT WILL BE IDENTIFIED BY OTHERS. STORMWATER MANAGEMENT AREAS ARE NOT DEPICTED.

2. REGULATED AREAS, INCLUDING FLOOD HAZARD AREAS AND RIPARIAN ZONES, ARE NOT VERIFIED, AND TO BE CONFIRMED BY NJDEP DURING THE APPROVALS PROCESS." Architectural Master Plan, Assumptions — Ci Design, 6/10/2026

Read those against the same sheet's own mapping: the site is ringed by wetlands lines, 50-foot wetland transition areas, two 300-foot riparian zones, a 150-foot riparian zone, an unnamed tributary, and Hop Brook — with the proposed subdivision line threading between them. The plan simultaneously shows how environmentally constrained the site is and disclaims that none of those constraints are verified, while omitting the stormwater areas entirely. Where stormwater management fits on this constrained site — and whether it pushes development into riparian buffers — is not answerable from the filed drawings.