Owner's Project Requirements (OPR) for Mission Critical Facilities
In a mission-critical facility, downtime is never a minor problem. It can mean a scrapped wafer lot, a compromised pharmaceutical batch, a halted medical device production line, or a data hall that goes dark for thousands of customers. There is little room for error, and a missed requirement costs more than money. That is why the owner’s project requirements matter so much in this sector. LotusWorks works with owners of Data Centers, Semiconductor, Pharmaceutical, and Medical Device manufacturing facilities, and the pattern is the same every time: the projects that perform best are the ones that write down the owner’s requirements before the first line is drawn.
This article explains what the OPR is, what it should contain for a mission-critical project, and how it connects to commissioning from the pre-design phase through operations.
Owner's Project Requirements
The owner’s project requirements are a written document that records what the owner needs from a building project: its functions, its performance, and how it will be operated and maintained. For a mission-critical facility, general statements are not enough. The OPR sets out the required uptime, the acceptable failure modes, the recovery expectations, and how resilient each system must be. In regulated manufacturing environments, it also records the process, product quality, and compliance requirements the facility must support.
The OPR is not a design, and it is not a specification. It states what the owner needs, not how the engineers should deliver it. That leaves the design team free to find the best solution, and it gives the owner a clear yardstick for judging the result. When a design choice supports the owner’s intent, it stays. When it introduces a single point of failure the owner never agreed to, the OPR gives the team the grounds to challenge it.
Commissioning Process
The commissioning process is a quality-focused approach that runs from the earliest planning stages through occupancy and beyond. Its purpose is to verify that building systems are designed, installed, and tested to meet the owner’s expectations. In mission-critical work, the process is more rigorous than in a typical building and usually includes staged testing at several levels. In pharmaceutical and medical device facilities, commissioning also lays the groundwork for qualification and validation activities
Construction Project
On a mission-critical construction project, schedules are aggressive, and the systems are complex. Power, cooling, controls, fire protection, process utilities, and security must all work together. Different contractors often install them on tight timelines. A gap in the requirements can stay hidden until late-stage testing, when it is most expensive and most disruptive to fix.
The OPR reduces that risk. When the project team starts from a shared, written understanding of the owner’s requirements, the electrical contractor, mechanical contractor, process contractor, and controls integrator all work toward the same targets. Scope disputes are easier to settle, because the question becomes whether something meets the OPR, not whose memory of a meeting is correct.
Energy Efficiency
Mission-critical facilities are among the most energy-intensive building types. A large data center can use as much power as a small town, and semiconductor fabs and cleanroom manufacturing facilities have very high energy and air-handling demands. Energy efficiency is therefore both an operating cost issue and a sustainability issue. The difficulty is that efficiency measures must never compromise reliability or product quality. The OPR is where that balance is set.
A useful OPR turns efficiency into measurable performance criteria. Examples include a target power usage effectiveness for a data center, an allowable range of supply air temperatures, a required economiser strategy, or cleanroom air change rates that meet classification without over-ventilating. It should also state which reliability and process requirements take priority when goals conflict. Cost belongs in the same discussion, because a more efficient design may cost more up front but pay back quickly at high loads. Efficiency also depends on the building envelope, air management, and controls, so the OPR should address them together rather than as separate topics.
Owner's Project Requirements (OPR)
The OPR is the owner’s statement of what success looks like. It is written before design begins and updated as the project progresses. It records project goals, functional requirements, load profiles, process requirements, growth plans, quality requirements, and the performance criteria the finished facility must meet.
For mission-critical owners, specificity is the point. A requirement such as “the facility must be highly reliable” cannot be tested. A requirement such as “the facility must sustain full critical load through the loss of any single power or cooling component, and during planned maintenance” can be. The second version tells the design team what level of redundancy is expected and gives the commissioning team a concrete test to run. The same applies in manufacturing. “The cleanroom must be clean” is an aspiration. “The cleanroom must maintain its specified ISO classification, pressure cascade, temperature, and humidity under defined operating conditions” is a requirement.
Owner's Project
The owner’s project is more than a building. It includes a business case, a budget, a schedule, and a long period of ownership during which the facility must keep working. A hyperscale or colocation data center operator, a semiconductor manufacturer, a pharmaceutical manufacturer, and a medical device manufacturer all have different risk tolerances and regulatory pressures. The OPR is where those tolerances are put in writing.
This is also where the owner’s voice matters most. Design professionals bring technical knowledge, but only the owner knows the cost of an hour of downtime or a lost batch, the growth forecast, the customer commitments, and the regulatory obligations involved. A good OPR keeps that knowledge from getting lost as the project team grows and the design moves forward.
Building Program
The building program describes the spaces, functions, and capacities the project needs. In a mission-critical facility, that covers technical space, support space, and the infrastructure behind them. Depending on the sector, that can include data halls, cleanrooms, fab and sub-fab areas, manufacturing and packaging suites, electrical rooms, mechanical yards, process utility plants, network rooms, and staging areas. The program says what is to be built. The OPR says how well it must work and how the owner will judge the result.
The two must stay aligned. If the program calls for phased expansion, the OPR should say what that means for capacity, redundancy during each phase, and how new load or new production lines come online without risking the live environment. When the documents reinforce each other, the design team gets a clear and consistent brief.
Process Scope
The process scope sets out which systems and assemblies will be part of the commissioning process. In a mission-critical facility, the scope is broad. It typically includes:
Electrical distribution, uninterruptible power supplies, generators, and switchgear
Cooling plants, air handling, and containment systems
Cleanroom HVAC, pressurisation, and environmental monitoring
Process utilities, such as ultrapure water, process gases, compressed air, and clean utilities
Building automation, power monitoring, and controls
Fire detection and suppression
Security and access control
Other specific systems that are critical to the owner’s operations
The OPR is the natural place to start defining that scope, because the owner’s priorities drive it. It should also state how deep the testing must go, from factory witness testing to integrated systems testing. Defining scope early makes fees and schedules easier to plan. It also avoids finding out late in the project that a key system was never included.
Project Delivery
The project delivery method affects how the OPR is used, whether that is design-bid-build, design-build, construction manager at risk, or another approach. Many mission-critical projects use design-build or fast-track delivery to meet market timelines, which makes the OPR even more important. When design and construction overlap, there is less time to catch misunderstandings, so the requirements must be clear from the start.
In design-build, the OPR often becomes part of the contract and gives the delivery team a defined target. With any delivery method, it is far easier to hold a team to requirements written before they were hired than to add new expectations once work is underway.
Building Commissioning
Building commissioning is the practical application of the OPR. The OPR states what the owner needs, and building commissioning provides the evidence that the finished facility delivers it. Reviews, inspections, functional tests, and documentation are all measured against the OPR and the design that grew from it.
For mission-critical facilities, the benefits are significant:
Fewer defects at turnover
Faster handover
Confirmed redundancy
A stronger foundation for qualification in regulated environments
Greater confidence that the facility can handle failures
Those benefits depend on the quality of the starting point. Commissioning against a weak or missing OPR can only confirm that equipment runs. It cannot confirm that the facility behaves the way the owner required under fault conditions.
OPR Document
The OPR document is the finished, written form of the owner’s requirements. It should be comprehensive, but that does not mean long for its own sake. It means complete enough that the project team clearly understands what is required. For a mission-critical facility, a comprehensive OPR typically includes:
Project description, project goals, and the owner’s intent
Uptime targets, redundancy topology, and concurrent maintainability requirements
Load profiles, process requirements, growth phasing, and capacity expectations
Owner’s expectations for energy efficiency, sustainability goals, and cost considerations
Environmental criteria for technical, production, and occupied spaces, including temperature, humidity, pressurisation, particulate levels, and indoor air quality
Applicable codes, standards, regulatory requirements, and certification or tier targets
Quality requirements for systems, equipment, and materials
Operations and maintenance expectations, including training requirements for facility and maintenance staff
Success criteria and how they will be measured
Supporting information, such as site conditions, utility data, or reference documents
The OPR is a living document. It should be reviewed and updated when the owner’s needs change or when major decisions are made as the project progresses. A version history helps everyone see what changed and why.
Commissioning Agent
The commissioning agent, sometimes called the commissioning authority, leads the commissioning process on behalf of the owner. The role is independent: the agent protects the owner’s interests and does not serve the design or construction teams. On mission-critical projects, the commissioning agent typically helps develop the OPR and reviews it for clarity and testability. The agent then uses it to guide plan review, site observation, and functional and integrated testing.
Many owners rely on their commissioning agent to run the OPR workshop, where stakeholders from across the organization share their needs. Operations teams, IT leaders, manufacturing and quality teams, and risk managers often have very different views of what “critical” means, and the workshop is where those views are reconciled. A skilled agent turns that conversation into specific, measurable requirements. This is the kind of work LotusWorks does for owners who cannot afford surprises after go-live.
Basis of Design (BOD)
The basis of design (BOD) is the design team’s response to the OPR. The OPR says what the owner needs, and the BOD explains how the design will meet those needs. It records the assumptions, codes, standards, calculations, and design decisions behind the chosen systems, including how redundancy and failure response will be achieved.
The relationship between the two documents is central to quality assurance. During plan review, the commissioning team compares the BOD with the OPR to confirm that nothing was lost in translation. If the OPR calls for continued operation during maintenance and the BOD shows a design that cannot support it, the gap can be raised while the drawings are still easy to change. ASHRAE Guideline 0 and Guideline 1.1 describe this documentation and are widely used as the reference for both the OPR and the BOD.
Building a Strong OPR
A few habits separate strong OPRs from weak ones:
Start early. Begin in the pre-design phase, before the design team has committed to solutions.
Involve the operators. The people who will operate and maintain the facility know the operational and maintenance realities that should shape the requirements.
Make requirements testable. Use measurable performance criteria, not general aspirations.
Use plain language. Owners, engineers, and contractors should all be able to read it.
Keep returning to it. Treat the OPR as the foundation of the project and check it at each milestone, including design development and construction, to confirm the project is still on track.
An OPR takes time and effort to create, but that investment is small next to the cost of an outage in a facility that was never meant to have one. It helps owners achieve the resilience they set out to achieve. It also gives every team member a shared reference point from the first meeting to the day the facility is fully in operation.
Conclusion and Next Steps
The owner’s project requirements are the foundation for every later commissioning activity, and nowhere is that clearer than in Integrated Systems Testing (IST). IST is the critical validation step between construction and live operation. It confirms that electrical, mechanical, controls, fire protection, emergency power, and life safety systems all perform together under normal and simulated failure conditions, and that the facility is ready for the loads it will carry. It is the last line of defence for catching anomalies, discrepancies, and issues, and it can only do that job well when the OPR has defined what “ready” means.
For owners and facility teams, the OPR and IST are two ends of the same process. The OPR states the redundancy, resilience, recovery logic, and operational performance the owner requires. IST proves those requirements were met before handover and creates the documented evidence base for ongoing compliance.
LotusWorks delivers Level 5 IST across mission-critical data center environments. That includes experienced ISCs, structured testing plans, site coordination, AHJ submission support, and comprehensive handover documentation. LotusWorks treats the OPR and IST as integral parts of the commissioning process, not standalone events at either end of a project.
Recommended next steps:
Engage LotusWorks early. The OPR should be developed in the pre-design phase, and IST requirements should shape design, documentation, construction sequencing, and schedule decisions. Involving the LotusWorks commissioning team before Level 5 avoids the most common integration failures.
Write a testable OPR and carry it into the testing plan. Uptime targets, redundancy topology, and measurable performance criteria in the OPR should flow directly into the integrated testing plan. Scope, sequence of operation, test protocols, safety procedures, acceptance criteria, and AHJ requirements should all be defined before execution begins.
Coordinate stakeholder availability. Confirm well in advance that owners, contractors, engineers, operations teams, and vendors are available for execution and retesting.
Plan for realistic failure scenario testing. Include utility failure simulation, blackout test procedures, redundancy path verification, and recovery logic validation, all traceable back to the OPR.
Maintain records for lifecycle compliance. Operations, audits, future modifications, and recurring five-year testing obligations require the OPR, basis of design, IST reports, integration matrices, test logs, and retest records.
Operational support should continue after IST. Preventive maintenance, periodic recommissioning, monitoring, and future integrated testing keep the facility aligned with the owner’s intent as equipment, loads, controls, and operating conditions change. Updating the OPR as conditions change keeps it useful throughout the facility’s life.
Contact LotusWorks
LotusWorks supports data centers, semiconductor facilities, pharmaceutical facilities, and medical device manufacturing facilities through every stage of commissioning, from Level 0 to Level 6. That starts with OPR development and design review, continues through factory witness testing, installation checks, startup, and functional testing, then Level 5 Integrated Systems Testing, and extends into post-handover operational support. Along the way, the LotusWorks commissioning team provides coordinated test planning, systems testing, documentation review, and handover support. To discuss your project’s OPR, commissioning, or IST requirements, contact the LotusWorks commissioning team.