>4.2K subscribers


We all know what value engineering is when it comes to buildings. Generally speaking, it is the process of trying to identify high-cost items with relatively low perceived value. Once you identify these items, you then remove them (if you can), replace them with alternatives, or find other creative solutions. All projects have to do this at one point or another because, well, money doesn't grow on trees.
One way to think about this is in terms of the following four-quadrant chart:

Low-value and low-cost items aren't expensive, so you will probably just leave them alone. But if you can move them up to the next quadrant, that's even better.
High-value and low-cost items are the ideal place to be. One example might be a low-cost material that gets applied in a creative way so as to create high perceived value. This is where design really becomes alpha.
Low-value and high-cost items are the fertile ground for value engineering exercises. If the perceived value is low, why spend the money on it? Surely there must be other options.
High-value and high-cost items, on the other hand, require the most thought and debate. How high value is it? Do we really need or want to spend the money on it? One example of this would be the architectural facade lighting at One Delisle. Sadly, it was not free.

Years ago, the team presented it as a possible value-engineering option. But ultimately, we viewed it as being fundamental to the overall design. Its perceived value was off the charts. I mean, why invest so much in the architecture only to cut the very thing that helps prominently display it? So a decision was made to keep it and, boy, am I glad we did.
There's nothing else going up in Toronto like it.
We all know what value engineering is when it comes to buildings. Generally speaking, it is the process of trying to identify high-cost items with relatively low perceived value. Once you identify these items, you then remove them (if you can), replace them with alternatives, or find other creative solutions. All projects have to do this at one point or another because, well, money doesn't grow on trees.
One way to think about this is in terms of the following four-quadrant chart:

Low-value and low-cost items aren't expensive, so you will probably just leave them alone. But if you can move them up to the next quadrant, that's even better.
High-value and low-cost items are the ideal place to be. One example might be a low-cost material that gets applied in a creative way so as to create high perceived value. This is where design really becomes alpha.
Low-value and high-cost items are the fertile ground for value engineering exercises. If the perceived value is low, why spend the money on it? Surely there must be other options.
High-value and high-cost items, on the other hand, require the most thought and debate. How high value is it? Do we really need or want to spend the money on it? One example of this would be the architectural facade lighting at One Delisle. Sadly, it was not free.

Years ago, the team presented it as a possible value-engineering option. But ultimately, we viewed it as being fundamental to the overall design. Its perceived value was off the charts. I mean, why invest so much in the architecture only to cut the very thing that helps prominently display it? So a decision was made to keep it and, boy, am I glad we did.
There's nothing else going up in Toronto like it.
Share Dialog
Share Dialog
1 comment
Fantastic to keep this. How go you mitigate the light shining in the units all night ? What about an effort to mitigate your contribution to a dark sky?