Case StudyA hospital combined a large UPS fleet with centralized monitoring and emergency service

Independence and trademark notice: this site is an independent technical publication. It is not affiliated with, endorsed by or sponsored by the manufacturers named. Manufacturer and product names are trademarks or property of their respective owners and are used only to identify public evidence.

Riello UPS reports that Cisanello Hospital built a fleet of 356 UPS units across about a dozen models and monitors them from a central control room. [1]

Published operating context

The manufacturer source identifies the customer, application and intervention. It is the primary evidence for the project facts. Guidance for another site comes from the separately identified technical references. No manufacturer result is represented as an independent measurement.

The published system protects operating rooms, intensive care, telecommunications, telephony, robotics, telemedicine and other critical activities. [1]

Figure 1: Published case sequence.

Reported challenge

Riello reports a December 24 intensive-care UPS failure that was replaced and returned to operation by December 26. [1]

Operational risk is not limited to a complete outage. A voltage variation, short interruption, transfer, weakened battery, overload, high temperature or unowned alarm can interrupt the protected function. The first task for a similar project is therefore to measure load, read the event history and name the consequence of interruption.

Published response

The manufacturer describes continuous maintenance, telemetry and backward-compatibility work as the hospital expands. [1]

The published sequence shows a solution selected for one context. It does not prove that the same rating, model, runtime or architecture fits elsewhere. A new project must confirm voltage, conductors, grounding, bypass, alternate source, clearances, environment and delivery route before purchase.

Figure 2: Evidence boundary.

Engineering qualification for another site

The design register separates known, measured, customer-stated, calculated and unresolved inputs. It covers normal watts and VA, peaks, runtime, power factor, phase loading, generator, temperature, cooling, batteries, communications and the work window. An unknown that changes safety, capacity, runtime or maintainability blocks firm selection.

States to prove include normal operation, source loss, stored-energy support, alternate source, static bypass, maintenance bypass, component isolation and return to normal. For each state, the record names the load path, remaining protection, reserve, permitted duration, alarms, switching authority and rollback condition.

Implementation controls

The purchase record binds the exact model, voltage, rating, batteries, bypass, accessories, network interface, certification, warranty and startup. A substitution requires a dedicated source and a fresh check of every criterion. Custom or non-cancellable equipment receives a separate release gate.

For intervention planning, review data-centre and critical UPS service. For equipment context, review UPS systems.

Figure 3: Case-specific decision matrix.

Reported results and measurement limits

The results above are manufacturer-reported. The public source is not an independent audit and may omit load profile, event logs, runtime tests, costs, failures, settings and observation duration. Those omissions do not disprove the published result, but they prevent conversion of that result into a guarantee for another site.

Records to carry forward

The closeout file retains the load survey, as-built one-line, models and serials, battery configuration, settings, firmware, transfer tests, alarms, deficiencies, corrections and final state. It also names the owner for alarms, updates, spares and the next lifecycle decision.

Subject-specific decision register

Four decisions govern this publication: 356-unit asset register, central telemetry and alarm triage, emergency replacement ownership and mixed-model compatibility and service. They form a reviewable register instead of a generic checklist. Each row has an input, source, owner, acceptance condition and consequence when evidence is missing.

The site survey records load, source, room, environment, bypass, delivery route and operating constraints [4]. Calculations and assumptions retain units, load state and source [5]. This connection prevents a catalogue value or a case outcome from becoming the default value for a new installation.

The state register separates normal operation, source loss, stored-energy support, static bypass, maintenance bypass, isolation and return [6]. It states what supplies the load, remaining protection, energized sources, permitted duration, alarms and the point where work must stop.

Monitoring identifies card, firmware, protocols, network segment, accounts, logs and alarm owner [7]. Read-only remains the starting point. A remote command or automated shutdown requires an approved need, dependency map and tested rollback.

Commissioning establishes criteria before testing and retains measurements, events, deficiencies, corrections and final state [8]. The service agreement states response, exclusions, spares, maintenance window, report and next lifecycle decision [9].

The cited GDF field pattern is used only for the comparable-project method [10]. It does not mean that GDF performed the manufacturer case. Customer facts, products, quantities and results remain attributed to the manufacturer source.

Sources

1. Riello UPS, Ensuring Continuity at Cisanello Hospital. https://www.riello-ups.com/uploads/file/947/3947/FLYPISX0Y25BREN.pdf
2. GDF Technologies internal knowledge library, UPS Monitoring Cybersecurity and Network Integration. Local library: Monitoring, SNMP & Shutdown/UPS Monitoring Cybersecurity and Network Integration.md
3. GDF Technologies internal knowledge library, UPS Service SLA Design and Coverage Scoping. Local library: Service Contracts & PM Agreements/UPS Service SLA Design and Coverage Scoping.md
4. GDF Technologies internal knowledge library, UPS Site Survey and Requirements Capture. Local library: UPS Solutions & Quotes/UPS Site Survey and Requirements Capture.md
5. GDF Technologies internal knowledge library, UPS Engineering Calculations and Independent Design Verification. Local library: UPS Solutions & Quotes/UPS Engineering Calculations and Independent Design Verification.md
6. GDF Technologies internal knowledge library, UPS Maintenance MOP Safety Boundaries and Go-No-Go Criteria. Local library: UPS Maintenance/UPS Maintenance MOP Safety Boundaries and Go-No-Go Criteria.md
7. GDF Technologies internal knowledge library, UPS Monitoring Cybersecurity and Network Integration. Local library: Monitoring, SNMP & Shutdown/UPS Monitoring Cybersecurity and Network Integration.md
8. GDF Technologies internal knowledge library, UPS Commissioning and Acceptance Testing. Local library: Installation & Commissioning/UPS Commissioning and Acceptance Testing.md
9. GDF Technologies internal knowledge library, UPS Service SLA Design and Coverage Scoping. Local library: Service Contracts & PM Agreements/UPS Service SLA Design and Coverage Scoping.md
10. GDF Technologies, GDF Field Case Library: Engineering and Quoting Patterns. Local library: UPS Solutions & Quotes/GDF Field Case Library - Engineering and Quoting Patterns.md