Excel Environmental Resources review of the North/West Battery Park City Resiliency Project
BPCA retained Excel Environmental Resources as its independent environmental monitor. Enovate Engineering, the contractor’s monitoring subcontractor, operates the project’s Community Air Monitoring Plan (CAMP) monitoring system. This dashboard translates Excel’s independent findings into plain language and maintains a rolling record as each new monthly report is released.
June also marked the first month in which Excel conducted two field inspections. During the June 5 inspection, Excel observed visible dust in Reach 5 and reported that active mitigation was not being used during one stone-handling operation until Excel raised the issue and water spraying began.
This section will always show the six most recent reporting months using the same resident-facing measures. Excel is BPCA’s independent monitor; Enovate operates the contractor’s CAMP monitoring system. As new Excel reports are released, the cards will update and older months will move to the archive.
*Monitor-count QA note: April and May appendix monitor-ID counts differ from Enovate’s narrative monthly summaries. The dashboard shows the monitor IDs visible in the appendices at month-end: April 15 vs. 14 stated in the summary; May 19 vs. 18 stated in the summary. June is consistent at 21.
Excel reported that it was not yet fully onboarded, conducted no onsite inspections, and did not yet have access to noise data.
Excel conducted one site visit on May 15. It did not observe visible dust during the visit, although remote monitoring showed PM events in Reach 1 and Reach 5 that day.
Excel inspected on June 5 and June 26. On June 5, it observed visible dust in Reach 5 and said additional water spraying began after Excel raised the concern.
Excel is primarily overseeing Enovate’s contractor-operated network. Excel’s own direct measurements were limited to periodic field inspections rather than a separate 24/7 independent monitoring network. Excel’s scope also indicates that event causes may be relayed as determined by the BPCA project team, so residents should distinguish independent review from fully independent cause attribution.
The reports use a mixture of design and apparent as-built monitoring plans, even though the underlying plans state that monitor locations may be adjusted in the field. A dated, “as-operated” monthly map is not provided.
June acknowledges micropile drilling in Reach 5E, but the inspection narratives do not separately document the Gateway-adjacent work area, reconcile the Reach 5E / Reach 6A North designation, or clearly identify which monitors served that work.
Enovate reports multiple monitor power disconnections, but Excel’s reports do not provide a resident-friendly monitor-by-monitor uptime and outage ledger. Future reporting should identify the monitor ID, cause and duration of each outage, whether another monitor provided adequate redundancy, whether the outage affected upwind/downwind site-contribution calculations, and when full monitoring was restored.
April notes negative rolling-average readings attributed to automatic calibration overcorrection. Excel says they should be treated as zero but does not quantify how often this occurred.
Based on GTA’s reconstruction of Enovate’s appendix data, documented power availability was approximately 93.9% in May and improved to 98.0% in June. April showed no documented April power disconnections during the defined active periods. These percentages measure only periods Enovate explicitly identified as disconnected from power; the reports do not provide an equivalent monitor-level ledger for mechanical, communications, maintenance, calibration, or damage-related downtime.
Enovate states that when wind speed falls below 1 mph, the downwind monitor is considered undetermined and site contribution cannot be calculated for that interval. GTA’s review of Enovate’s published wind-rose summaries found very low-wind conditions were common. In June, 21 of 34 wind-rose reporting blocks (62%) showed calm and/or sub-2 mph conditions for at least half of the reporting period.
Because Enovate groups winds below 2 mph rather than separately reporting the exact time below 1 mph, the percentage of intervals in which site contribution was unavailable cannot be determined from the published reports.
Important: The 62% figure is a low-wind screening indicator, not a measure of the percentage of time site contribution was unavailable.
Excel identifies events where stronger mitigation, work stoppage, BMP re-evaluation, or other action should have occurred.
A resident-friendly corrective-action register: date, issue, required response, who was notified, what was done, when Excel verified it, and whether the item is open or closed.
For each Level 2 event, identify whether work stopped as required, what controls were re-evaluated, when conditions returned below the applicable threshold, and when work resumed. This is the most important unresolved compliance/accountability question.
Provide a dated monthly map and inventory showing every active air, noise, and vibration monitor; monitor ID; installation, relocation and removal dates; and all periods of unavailable or invalid monitoring. Downtime should be classified by cause, including power loss, equipment failure, communications failure, maintenance/calibration, relocation, physical damage, or another cause, with backup coverage identified.
Report, by Reach and month, the percentage of valid 15-minute intervals in which wind conditions allowed a meaningful upwind/downwind site-contribution calculation, including the number of intervals excluded because wind speed was below 1 mph.
Publish an event-by-event corrective-action register showing the date, issue, required response, party notified, action taken, Excel verification date, and whether the issue is open or closed.
State when Excel received full access to noise-monitoring information, whether earlier months will be reviewed retroactively, and how independent noise findings will be incorporated into future reports.
Explain material count discrepancies, including Excel vs. Enovate PM-event totals — especially May — and Enovate’s April/May narrative monitor counts versus the monitor IDs shown in the appendices. Future reports should use a dated, as-operated inventory and internally consistent totals.
Explain which monitors covered the Gateway-adjacent work, when that monitoring began, how Reach 5E and Reach 6A North terminology should be reconciled, and whether the configuration provided meaningful receptor and upwind/downwind coverage.
This reference section explains the technical shorthand used above. Linked terms throughout the dashboard jump here for readers who want more detail.
The project's CAMP establishes how construction-related air monitoring is performed and sets short-term response thresholds known as Action Levels. The purpose is to trigger protective action during construction when particulate levels rise.
↑ Back to topPM means particulate matter: tiny airborne solid particles and liquid droplets. The dashboard counts short-term PM Action Level events reported by the project monitors; these are not automatically the same thing as violations of longer-term regulatory air-quality standards.
↑ Back to topPM10 refers to inhalable particles with aerodynamic diameters generally 10 micrometers or smaller. Construction dust can contribute to PM10, which is why the CAMP monitors it separately.
↑ Back to topPM2.5 refers to fine particles with aerodynamic diameters generally 2.5 micrometers or smaller. These particles are smaller than PM10 and are monitored under their own CAMP thresholds.
↑ Back to topLevel 1 is the lower CAMP response threshold. When construction-related particulate levels reach this level, the plan calls for additional or re-evaluated dust-control measures while work may continue only under the applicable CAMP conditions.
↑ Back to topLevel 2 is the higher CAMP response threshold. After required suppression efforts, an applicable Level 2 condition requires work to stop, controls to be re-evaluated, and work to resume only after particulate conditions are reduced below the applicable threshold and visible migration is controlled.
Why GTA highlights it: Level 2 events provide an especially important test of whether the project's required protective response was followed.
↑ Back to topThe contractor compares upwind and downwind readings to estimate the portion of particulate levels that may be attributable to construction. Wind direction is therefore central to the calculation. When wind is too light to determine a downwind station, the project may be unable to calculate a site-contribution value even though raw monitor readings still exist.
GTA has therefore asked BPCA to explain the siting rationale for each reach and to provide dated, as-operated monitor locations together with wind direction, monitor relocations, outages, and any supplemental or mobile monitoring used when fixed locations do not create a meaningful upwind/downwind comparison.
The dashboard does not characterize west-to-east winds as the prevailing condition for all periods unless supported by the project's own meteorological data. The concern applies specifically during periods when wind direction makes a north–south monitor pair crosswind rather than upwind/downwind.
↑ Back to topLow-wind reporting limitation: Enovate’s wind-rose summaries group conditions into “calm” and “<2 mph” categories, while the CAMP site-contribution cutoff is <1 mph. As a result, the published reports do not provide enough detail to calculate the exact percentage of intervals when site contribution was unavailable because of low wind.
A site inspection is an onsite visit by Excel, BPCA's independent monitor. Excel also reviews the contractor's monitoring data remotely. A site-inspection count therefore should not be read as the number of days environmental monitoring occurred; the contractor-operated monitors run separately.
↑ Back to topThis dashboard reports noise information only when Excel's monthly reports provide enough information to do so. Excel reported that it did not yet have noise-monitoring access in April and May and was reviewing Enovate noise reports in June. “Not available” does not mean zero noise events.
↑ Back to topThe reporting-delay figure is the number of days from the end of the reporting month to the date shown on Excel's public monthly report. It measures when residents received the report, not whether Excel communicated particular concerns to the project team in real time.
↑ Back to topThe project is divided into numbered construction areas called Reaches. The visual below is more intuitive for community use because it shows the full Battery Park City project alignment and all seven reaches.

Why this matters: environmental-monitoring results, monitor locations, outages, work activities and Excel observations are often reported by Reach rather than by familiar building, park or street name.
What the first Excel reports covered: April–June monitoring discussion in Excel’s reports focused mainly on the reaches that were active or producing events during that period, especially Reaches 1, 3, 5, 6 and 7. Even so, this GTA dashboard is intended for the broader Battery Park City community, so it should orient residents to all reaches, including Reach 2 and Reach 4.
Reach 5E / Reach 6A North: the Gateway-adjacent area deserves particular care in interpreting the reports. Excel’s June work summary identifies micropile drilling in Reach 5E, while other project materials and community discussion also refer to the nearby area as Reach 6A North. The dashboard flags this as a monitoring-documentation issue rather than silently treating the names as interchangeable.
Resident-facing recommendation: future independent reports should include a dated “as-operated” map showing the actual location of every active air, noise and vibration monitor, along with installation, relocation, removal and outage dates.