In New York City and select jurisdictions, FDNY mandates ARCS systems in place of standard BDA / ERCS solutions. Most other AHJs continue to accept BDA systems. The determining factor is always the Authority Having Jurisdiction, not installer preference.
Yes. FDNY ARCS requirements are specific, prescriptive, and documentation-heavy. System architecture, labeling, monitoring, drawings, and submission language are all scrutinized. Small inconsistencies routinely result in objections months after submission.
Yes. If drawings are not available, Marconi’s in-house engineering team can develop a compliant design and price based on building information and jurisdictional requirements. Once pricing is approved, shop drawings and submissions are produced.
Failures usually don't come from hardware. It comes from:
• Incomplete or incorrect documentation
• Inconsistent labeling or terminology
• Misalignment with AHJ expectations
• Paperwork handled after installation instead of in parallel
These issues are preventable. We manage documentation and compliance in parallel with production, which is why our projects consistently progress toward approval on schedule and achieve industry-leading on-time delivery rates.
Marconi designs systems with inspection and sign-off in mind from the start. Engineering, documentation, and production move together, not sequentially. This prevents scenarios where systems are installed correctly but cannot be approved.
Marconi designs and manufactures FDNY-compliant ARCS systems and supports projects through engineering coordination, documentation, delivery, and sign-off. Final approval is always granted by the AHJ, but Marconi systems are built to meet FDNY standards and expectations.
Marconi systems ship as complete, factory-built assemblies, not loose components. Connection points are clearly labeled, system configuration is handled in-house, and integrators are installing (not building!) systems in the field.
For larger or ongoing projects, Marconi conducts bi-monthly project check-ins with larger projects. Every active job is reviewed, bottlenecks are identified, and next steps are clarified. Accountability is shared, and issues are addressed before they become delays.
Yes. Custom builds are a core capability. Whether the requirement is jurisdiction-specific, building-specific, or operationally unique, systems are engineered accordingly without overcomplicating installation or approvals.
Depending on jurisdiction, this may include:
• Engineering coordination
• Shop drawings
• Submission-ready documentation
• Review of AHJ-specific terminology and labeling
• Support through testing and sign-off
Exact requirements vary by AHJ.
Because Marconi manufactures in-house and maintains inventory, lead times are consistently strong. In time-sensitive situations, systems can move quickly once approvals and paperwork allow. Technically, we could even ship out a system to you by tomorrow!
No. While Marconi is deeply experienced with FDNY ARCS systems, we also support BDA, ERCS, and in-building communications nationwide, adapting designs and documentation to local AHJ requirements.
Anyone responsible for system compliance, installation, or sign-off (including integrators, engineers, and project managers) can reach out directly. Early involvement typically reduces downstream risk.
Design
Paperwork
Delivery of system
System installation
Troubleshooting