Transcript Notes: Fire Alarm, ERX, COs, and Schedule Coordination

Fire Alarm Coordination and Drawings

• Walk-through with the fire alarm designer today; still a couple of items the designer must fix.
• Inspections: I canceled the inspection for tomorrow because they needed to know before noon, and we’re not ready yet.
• Target inspection date: ideally Wednesday, subject to the designer’s availability.
• RFIs (Requests for Information): Pulled together all information for the fire alarm designer, but concern remains that something might be missing.
• Proposal: Suggest getting in touch with the fire protection PM to sort offline; a call with Advanced Automatic if needed.
• John sent a link for fire protection drawings this morning; review opened but not fully resolved; drawings are helpful though a bit opaque (the speaker is an electrician by trade).
• Plan: hop on a quick phone call to sort out questions; fire alarm designer is off today but returns tomorrow; will touch base with him then.
• If unresolved after that, set up a call with Advanced Automatic.
• Expectation: much of the needed information will be found in the protection drawings; remaining questions to be addressed tomorrow.
• Elevator question: does the elevator have a backup battery? Yes, it does. Located in the control room.
• ERX (Emergency Response Exchange) system: second test not yet done because rock and doors are not fully installed; expected in a week or two.
• ERX scope: the test will determine whether ERX is needed on Level 4 only or on Levels 1–3 as well; head-end equipment is in Level 4 IDF Closet.
• RFIs on ERX: the conversation was satisfactory for the moment; come back if more is needed.
• Summary: we’re not missing something if more is needed; we’ll reconvene as questions arise.

Change Orders and Contractual Discussion

• Change Order (CO) discussion underway; plan to talk contractually given the end-of-project funding situation and budget constraints.
• CO for overtime: first CO shows up with an incorrect year; speaker is willing to sign and return once clarified.
• Access control CO: there was a missing record (the team can’t find “12 r one, Joe”); author confirms they’ll locate or resolve.
• “Coming in hot” CO: noted as done; verbiage is incorrect and needs editing.
• CO 15 (Panel Layout): back-and-forth about panel relocations; original relocation to avoid putting panels in firewalls and stacking; later relocation to original locations increased cost; question about who bears the cost for these relocations; estimated around two to three fifties (two to three $50k units) – requires confirmation; the speaker can accept an amount once clarified.
• Panel relocation rationale: panels were relocated to avoid firewall stacking; evaluation of cost impact; speaker will compare the relocation cost against original plan.
• Note: speaker is reconstructing the sequence to understand the cost drivers and what portion should be borne by the contractor.
• Question: drove the unit panel relocation? Answer: it was architectural; intended to avoid placing panels in firewalls and allow stacking; cost impact to be reviewed.
• Action: create a note to remove “electric remote” from the COs and proceed with the rest.
• CO 15 panel layout discussion continues; panel relocations discussed at length last year; confirm feasibility and cost impact.
• 4242 Comcast Raceways: two raceways listed; need approval for one three-inch Raceway from Impo to Level 3 riser and one two-inch Raceway; speaker asks for approval.
• Circulation pumps, microwave circuit, and smoke doors: end-of-project CO cluster; these are equipment shown on drawings but power not yet accounted for in electrical drawings.
• Concept: these COs represent equipment shown on drawings but not fully captured in plans; contract interpretation needs alignment (contract says if it requires power, full system is provided; the current proposal may only include shown equipment, not necessarily all associated power).
• Contractor stance: early on they were permissive due to lack of budget, but now cost is stacking up; a middle ground is needed with Noel (the other party) to avoid escalation.
• Labor rate consideration: offer to lower labor rates as a goodwill lever to reduce CO costs; still propose a contractual discussion with Noel to avoid unilateral changes.
• Grouping COs: propose lumping certain COs (e.g., circulation pump, Comcast-related items) for a broader discussion.
• Refrigerator circuit CO (73): field-directed changes; dedicated refrigerator circuit in a community room; verify if this was correctly captured; may be a couple thousand dollars; plan to re-check drawings.
• FSDs (Fire and Smoke Dampers) on the Second Floor: field updates show location changes; mechanical contractor may not know exact locations; need to finalize placements; possible that several FSD control units were missed and need to be installed; plan to re-check drawings.
• Additional security power CO: dedicated circuit from electric room to Level 4 IDF to support Shear’s equipment; distance led to use number eight conductors; status: completed by Lalo previously; no further action required at the moment.
• Summary: plan to talk with Noel to settle contract terms; the goal is fairness and avoiding project-wide conflicts; keep COs within reasonable bounds while recognizing the contract language.
• Additional COs and field-directed changes: 58 (bulletin 12) light fixture changes rolled into a global CO; void or stand down if included in last CO; 63, 68, 70 (FSDs) validated as in-scope or to be completed; 73 (refrigerator circuit) reviewed; 62 (circulation pump) and structural items discussed; plan to lump items and revisit with Noel.
• Final stance: try to reach a middle ground on COs; reduce risk of escalation; keep COs from pushing into hard limits of the contract.
• Administrative note: there is an ongoing discussion to add lower labor rates as a concession if needed; avoid a full contract confrontation.

Scheduling, Budget, and Billing Pressure

• We’re near the end of the project; funding is essentially exhausted; this drives the urgency to settle COs and avoid new large costs.
• The speaker acknowledges overbilling in prior invoices to keep finish and trim costs in front; this has led to a front-loaded billing stance, making current invoices look aggressive.
• They bill at the beginning of each month projecting where the job will be; in this month, there’s a perception that some costs are already shown in last month’s invoice rather than current progress.
• Plan: push CO approvals into September billing; communicate that COs will be sent over the next few days but billed in September to smooth cash flow.
• Acknowledgement: the speaker wants to avoid a debt trap or a situation where the client can pull back due to a lack of control; the priority is mutual fairness and avoiding escalation.
• Action: prepare to offer cost-Contingency-based reductions (e.g., lower labor rates) as a negotiation tool; keep the process within contract terms and avoid adversarial escalation.

Schedule, Logistics, and Site Logistics

• Endgame: switchgear installation is a major upcoming milestone; this remains a hurdle and a focal point for the project’s next phase.
• Timeline note: the switchgear date was previously targeted but has not progressed as hoped; a weekly update from the switchgear supplier (Mills) was requested; no robust response yet.
• Temporary power and lighting from CES: some temporary lighting and power were purchased; must back these costs out of the contract as non-permanent items; current location of these temporary items needs clarification.
• Temporary power generator: scheduled for this week, but unlikely to happen; Otis mobilization is expected this week, with generator needs likely about two weeks out.
• Change order for temporary power connections to the panel is expected; discuss whether to quote in advance or handle as a later change.
• Plan: coordinate with all parties to ensure temporary power and generator arrangements are properly documented as COs; avoid last-minute surprises.
• Site cleanliness and space management: request to consolidate and clear material from the garage as other trades come in; plan to create a dedicated dark space; a cleanup clean-up is planned for next week; acknowledge the electrical room is expanding and will not stay oversized for long; improvement in organization desired.
• Logistics note: speaker acknowledges their own mess and appreciates the team’s patience; emphasis on maintaining progress and clean space to allow other trades to work efficiently.

Communications, Next Steps, and Key Actions

• Immediate actions: follow up with fire alarm designer tomorrow; if needed, arrange a call with Advanced Automatic; confirm RFI responses on fire alarm circuits and panel connections.
• Coordinate with Noel on contract terms; aim for a fair agreement that avoids escalation while staying within project budgets.
• Schedule coordination: set a time to review COs with Noel to resolve costs and responsibilities; consider lowering labor rates as a negotiating tool.
• Documentation: ensure all changes are properly captured in the SOV (Schedule of Values) and that the correct year is reflected on change orders; fix any wording or typos in change orders (verbiage corrections noted for CO 15).
• Financial planning: align billing with project milestones; push CO approvals into September billing; monitor overbilling situations going forward; maintain transparency with the client.
• Future milestones: monitor switchgear schedule and follow up weekly; coordinate material clearance after James completes his unit sequence; plan to finalize the electrical room configuration to free up space for subsequent trades.
• Final sentiment: both parties want a productive, fair path forward; avoid adversarial disputes; maintain a professional, collaborative tone even when discussions get tense.

Key Definitions and Concepts (for quick study)

• RFIs: Requests for Information used to clarify project details that are not fully specified on the drawings.
• ERX: Emergency Response Exchange system; head-end equipment location is confirmed at Level 4 IDF Closet; testing scope includes determining whether Level 4-only or Levels 1–3 are required.
• IDF/ MDF: Indoor Distribution Facility / Main Distribution Facility; Level 4 IDF Closet referenced as the head-end equipment location for ERX.
• CO (Change Order): Formal documentation of scope changes, cost adjustments, or schedule changes during construction.
• SOV (Schedule of Values): A mechanism used to track costs against the project budget and line items; changes are often tracked here for billing.
• FSDs: Fire and Smoke Dampers; field-directed changes can affect location and scope.
• DAISY-CHAIN: In this context, a single circuit daisy-chained to multiple panels/pieces of equipment (panel and booster panels) as a preferred topology for power distribution.
• Temporary power/lighting: Non-permanent electrical support used during construction; needs to be accounted for in COs and later removed.
• Ventilation and mechanical field changes: Changes to roofing, façade routing, and mechanical rooms can drive CO costs.

Connections to Foundational Principles

• Change management: This transcript demonstrates typical late-project risk management where scope creep, budget limits, and contractual interpretations collide; emphasis on documenting decisions, negotiating with a partner (Noel), and avoiding escalation.
• Integrated project delivery concerns: RFIs, drawings, and field directives require cross-discipline coordination (electrical, fire protection, mechanical) to ensure the system is installed per updated drawings and field conditions.
• Ethical and practical considerations: The conversation highlights balancing fairness, budget constraints, and project timelines; the goal is mutual success without destroying working relationships.

Notable Examples and Scenarios from the Transcript

• Scenario 1: Fire alarm issues identified during a walk-through that require further fixes before the final inspection; a phone call with the designer or Advanced Automatic is planned to resolve outstanding questions.
• Scenario 2: ERX system testing strategy hinges on whether Level 4 is sufficient or if Levels 1–3 are included; this determines the extent of head-end equipment and tests.
• Scenario 3: Panel relocation cost implications due to moving electrical rooms and re-locating panels; the team debates who bears the cost and how this aligns with the contract.
• Scenario 4: Field-directed changes (e.g., FSDs and dedicated circuits) may not be fully captured by the plans; a contractual alignment is needed to decide whether these are COs or in-scope alterations.
• Scenario 5: Endgame finance: near project completion with exhausted funds; the team contemplates pushing CO costs into September billing and reducing labor rates to reach a middle ground.

Formulas, Equations, and Specific Numeric References

• Conduit and Raceway sizing references:
  • $1 \times 3'' \text{ Raceway}$ from Impo to Level 3 riser
  • $1 \times 2'' \text{ Raceway}$ (two-inch raceway)
• Conductor sizing reference:
  • $\text{AWG }8$ conductor used for security power circuit traversing a long distance to Level 4 IDF.
• Schedule reference:
  • Planned switchgear date: $\text{26th (September)}$ (date cited in discussion)
• Physical locations:
  • Head-end ERX equipment located in the Level 4 IDF Closet
• Notation of cost language:
  • Phrases like "two, three fifties" indicate a rough cost estimate in the discussion, to be clarified later with exact figures.

Summary of Practical Takeaways

• Align RFIs and drawings early with the fire protection team to minimize last-minute questions.
• Confirm the ERX scope and ensure the Level 4 IDF Closet contains the necessary head-end equipment and that testing aligns with project priorities.
• Address COs promptly, focusing on clarity of scope, responsibility, and fair cost-sharing; use labor-rate adjustments as a negotiation tool if needed.
• Maintain transparent billing practices and plan COs for September to smooth cash flow and avoid compounding issues.
• Plan for site logistics and space management as trades converge; prioritize a clean, organized workspace to prevent schedule delays.
• Maintain ongoing communication with all stakeholders (Noel, Mills, John, Advanced Automatic) to prevent delays and misinterpretations.
• Keep the big-picture goal in mind: finish the project on schedule, within budget, and with properly installed and commissioned systems that meet the fire and safety requirements.