Owner's Project Requirements

Purpose of the Process
  • Conveys the owner’s requirements to all involved with the project - what will be accomplished
  • Establishes measurable success criteria
  • Provides an approved set of project requirements and guidelines for the project team
  • When done early in the project process, it simplifies the Programming and Basis of Design efforts

Best and most effective when this is the first document produced by the owner to identify project needs…

AND...Highly recommended regardless of project status

Without an OPR, you are “flying blind”

Benefits of the OPR

There are numerous benefits. The earlier the institution can define the strategic objectives and goals that it is trying to accomplish (its business objectives), and can translate these objectives into project specific requirements, the more streamlined the project processes can become when the project is funded and ready to be planned and executed.

Benefits during:

Pre-project Planning and Pre-design:

  • The development process fosters collaboration and respect between stakeholders.
  • It ensures that stakeholders reach consensus on priorities EARLY.
  • It provides direction to the design team, clear understanding of the Owner's needs and priorities.
  • Contractors know what the Owner expects, not just the A/E's interpretation.
  • Provides a pass/fail criteria for testing; ensures that systems operate as intended.
  • Allows O&M staff to set original goals, including expectations and limitations, and captures the "why's."
  • Even though stakeholders have input into the OPR, not all members that use the document will have been involved in the OPR process.

The OPR is the Heart of the Project Planning Process
  • It defines in writing how the owner will measure the success of the project
  • It seeks early input from all stakeholders, including the Owner, operations and maintenance, technical staff, building users, and occupants, and other stakeholders, as applicable.
  • It provides guidance throughout the project for designers and contractors.
  • It becomes a “living” document, and is updated as decisions are made.

How OPR Differs from Programming
  • It is a more strategic discussion, that seeks to define the Institution’s business objectives, and then identifies project specific goals and “Investment Metrics” that meet those Business Objectives.
  • It establishes measurable performance success criteria, benchmarks, and supporting information that must be met by the Programming Phase.
  • The Programming document further defines and documents specific requirements, incl. space and functional requirements, and develops cost models.