Build a Campus UPS Tender with Common Requirements and Site Schedules
By Highidea Power · 21 October 2026 · 5 min read
A multi-building UPS tender works best with two layers: a common specification for purchasing and operations, plus a site schedule for each installation. Standardize how suppliers describe equipment, documents, monitoring and acceptance. Keep voltage, load, runtime, cabinet fit and local conditions specific to each building. This allows repeatable procurement without forcing unlike sites into one model.
Highidea Power offers rack, tower and external-battery UPS configurations and supports application-based selection. For a campus project, a structured site list helps our team propose reusable configuration groups while keeping the exceptions visible.
Decide what the campus wants to share
Start with the people who will operate and maintain the systems. A central IT team may want a consistent alarm vocabulary and asset naming convention. Procurement may want one response format and an agreed document language. Facilities may need a clear installation handover for each building.
These are useful common requirements because they make systems easier to buy and manage. They need not imply identical ratings, battery arrangements or interfaces everywhere. If an existing platform requires a particular monitoring function, describe the function and receiving system, then obtain a response for each offered host/card combination.
Common requirement | Define centrally / Keep local differences visible |
|---|---|
Offer format | Define centrally Model, quantity, included scope and exceptions Keep local differences visible Different equipment or installation work |
Asset records | Define centrally Campus/site/system identifiers and document links Keep local differences visible Exact installed host, battery and option identities |
Monitoring | Define centrally Required messages, ownership and receiving platform Keep local differences visible Network access and supported card/interface |
Documents | Define centrally Language, revision naming and handover contents Keep local differences visible Model-specific instructions and drawings |
Acceptance | Define centrally Required record fields and responsible roles Keep local differences visible Load, test conditions and allowed operating outcome |
Support coordination | Define centrally Contact route and information to retain Keep local differences visible Access hours, local custodian and service constraints |
Keep electrical and IT requirements separate enough for the correct reviewers to answer them. A common email notification requirement, for example, does not confirm that every proposed card supports the same network security or shutdown integration.
Give every installation a site schedule
Use one schedule per actual installation, including more than one in the same building where loads or sources differ. Record who supplied the information and when it was checked. The rack UPS RFQ template provides detailed technical inputs; the campus schedule adds location, ownership and grouping.
For each site, collect:
- The protected devices, representative W and VA, startup conditions and forecast changes.
- Required runtime and the purpose of that time: continued service, alternate-power arrival or orderly shutdown.
- Source, output and bypass requirements, as applicable, including voltage and frequency.
- Rack or floor location, usable depth, support limits, connections, ventilation and service access.
- Monitoring network, receiving team, site access window and installation dependencies.
- The survey owner, open questions and the date by which those questions must close.
An unknown value remains an assigned survey task. Avoid copying a neighbouring building's load simply because both rooms contain similar switches.
Group sites only after reviewing the differences
A configuration group is a reusable procurement description for sites whose relevant requirements have been checked. It can simplify quoting, spare planning and document management. It is not a permission to swap equipment between any sites carrying the same label.
In this hypothetical example, no capacities or runtime figures have been assumed:
Site | Required task / Likely grouping decision / Information that can change it |
|---|---|
Teaching-block network closet | Required task Maintain agreed network services Likely grouping decision Candidate for a repeated closet configuration Information that can change it PoE load, cabinet depth and local voltage |
Administration server rack | Required task Support a planned shutdown sequence Likely grouping decision Separate from a network-only closet Information that can change it Application dependencies and shutdown duration |
Core communications room | Required task Maintain central network services Likely grouping decision Review as its own configuration Information that can change it Source arrangement, redundancy and service method |
Two teaching-block closets may join one group after their differences are resolved. The core room should not inherit that group merely to achieve one stock code. Similarly, one larger UPS does not by itself answer whether backup should be centralized; that is a separate rack-versus-room architecture decision.
Ask suppliers to answer at group and site level
The group response should state the offered host, batteries, options, supplied installation parts and document list. The site response should identify the group being used and every deviation. Keep a quantity reconciliation so a late building addition does not disappear between the site list and the bill of materials.
Use a short decision line for each proposed exception:
Site: __. Common/group requirement: __. Offered difference: __. Effect on installation, monitoring or operation: __. Reviewer: __. Accepted/revise/open: __.
This turns a catalogue-based response into a manageable procurement record. It also lets the campus accept a justified local variation without changing the common specification for all buildings.
Separate delivery, installation and operational handover
Procurement completion is one milestone. A particular building can still be waiting for its room, network access or qualified installer. Maintain a site status list that distinguishes equipment delivered, installation prerequisites complete, commissioned under the approved plan, and handed over to the operating team.
For the handover, retain the actual serial/configuration identities, document revisions, approved results, open exceptions and alarm recipients. Agree a representative test approach with the responsible engineers and IT team; do not perform live outages to demonstrate campus consistency.
Our ET1-3KR rack-mounted online UPS, with built-in LiFePO4 storage, is one starting point for suitable rack applications. Other runtime, voltage or installation requirements can call for a different configuration. Share the actual site schedules so the proposal matches the campus rather than a generic building label.
Continue the campus proposal
Our application-selection and OEM/ODM services support discussions around load, voltage, runtime, installation and monitoring. Send the common specification and site list, including the unresolved survey questions, to begin a grouped proposal.
Product and planning references
FAQ
Frequently asked questions
Should every building use the same UPS model?
Use the same model where the relevant requirements genuinely match. Standardized records and support coordination can still be maintained across different models. A shared part number should follow engineering fit, not replace it.
How should we handle a building added after tender release?
Assign it a new site schedule, check whether an existing group applies and revise quantities and dependencies. Keep the accepted revision identifiable so suppliers and installers work from the same list.
Can we specify one campus-wide runtime?
You can state a common target where the operational task supports it, but record the corresponding load at every site. Different loads can require different storage even with the same runtime target.
Put this into practice
Need help specifying the right unit?
Share the load, voltage, runtime, environment and destination for a configuration review.