Liveblogging Sidewalk Labs’ Master Innovation and Development Plan, Entry 32: The MIDP Volume 2, The Innovations, Chapter 5: Digital Innovation, Introduction

Posted on August 20, 2019 by bhaggart

A series of posts built “from the internet up”

Previous Master Innovation and Development Plan liveblog entries and relevant documents available here

There’s a lot to unpack in this chapter, so I’m going to divide it into five (5) posts. That’s a lot of reading, and even more writing, so let’s get started.

Chapter 5: Digital Innovation (pp. 374-463)

Introduction (pp. 376-383)

For some strange reason, Sidewalk Labs has left to the end of its volume on Innovations its discussion of how it will make the Quayside etc. district a smart city. It’s an odd move, when you consider that:

  • the only logical reason the unproven company Sidewalk Labs was hired was because of its connection to Google, the most digital of the digital companies. The digital is supposed to be its competitive advantage;
  • so many of the preceding “innovations” depend on digital connectivity and data collection to function, which would seem to make leading with the underlying system a no-brainer;
  • its initial sales pitch in its response to the Waterfront Toronto Request for Proposals, was that it would build “the world’s first “neighbourhood from the internet up” (Project Vision, p. 15). The phrase “from the internet up appears nine more times in that document; and
  • most importantly, the treatment of data, surveillance and privacy were what has been (rightly) subjected to the most sustained, principled, and coherent public criticism.

The reason, of course, isn’t really strange at all. From the very beginning Sidewalk Labs and Waterfront Toronto have always been more comfortable talking about cool potential new physical technologies than the data that necessarily makes these smart-city things possible. Back in the pre-Facebook/Cambridge Analytica days, attaching “connectivity” and “the internet” to everything was still seen as a winning public-relations strategy. However, now that people are beginning to understand the pervasive surveillance and data collection needed to run a Quayside-style project in the way envisioned by companies like Sidewalk Labs, that calculation has changed.

And so, the details of how Sidewalk Labs will set up its surveillance network (which is what it is, even though the word “surveillance” appears only twice in the entire MIDP) are buried in the last possible section.

Still, addressing digital and data issues 1,154 pages into a report is better than never discussing them.

Four questions I’ll be keeping in mind:

  1. How Sidewalk Labs situates itself in its proposed governance structures.
  2. The degree of flexibility when it comes to data governance.
  3. The role of standards in this project: who is setting them, and their effects.
  4. The level of detail provided – I’ll want an advance over Sidewalk Labs October 2018 digital governance proposal.

What I’m not expecting:

  • Any major input from Waterfront Toronto, even though they’re the public authority who ideally whould be leading this debate (granting the reality that they lack a deep digital bench).

It’s the final chapter of Volume 2. Let’s go.

Their identified goals (p. 377)

  • affordable digital infrastructure
  • digital infrastructure that is “open to everyone” (everyone? Quality standards for companies that want to piggyback on this infrastructure (will it be public?)

Urban data

information gathered in the city’s physical environment, including the public realm, publicly accessible spaces, and even some private buildings. (p. 377)

That covers a lot of ground.

It’s the surveillance, stupid

This formulation is incorrect:

While Canada has a strong foundation of privacy laws around personal information, and recognizes privacy as a fundamental human right, urban data creates a new set of questions that have surfaced during the Sidewalk Toronto public consultation process.

It’s not “urban data” that creates a new set of questions. It’s Sidewalk Labs’ desire to institute a new system of pervasive, ubiquitous surveillance in all public spaces “and even some private buildings” that “creates a new set of questions.”

Talking about “urban data” is a way of reframing the surveillance question so you don’t have to use the word “surveillance.”

Never on the table: Minimized or no pervasive surveillance, just: how can we classify the data we collect?

Who should set data-governance regulations?

  • Sidewalk Labs is big on arguing that the Eastern Waterfront is the appropriate “scale” on which to realize its dreams. Why is a tiny parcel of land in Toronto the appropriate scale to test out data-privacy and surveillance laws and institutions, and not either Ontario or Canada?
  • Why does it make sense to create new data and surveillance laws at this level, with none of the parliamentary review process of other levels of government?
  • What happens if the governments of Ontario or Canada eventually develop comprehensive data- and surveillance laws that contradict Sidewalk Labs’ regulations?
  • Federal or provincial regulatory changes could presumably affect the degree of profitability of Sidewalk Labs’ Eastern Waterfront investment. Would it threaten to pull out of Toronto?

It would be unseemly if Sidewalk Labs were to use its presence as a de facto governing entity in any Eastern Waterfront development as a stick with which to threaten Canadian governments to develop laws in its or Google’s narrow economic interest.

  • Will Sidewalk Labs and Google commit to not lobbying the federal or provincial governments on data and surveillance regulations, given this conflict of interest?

clear standards that make data publicly accessible, secure, and resilient (p. 377)

  • Should all data be publicly accessible?

Standards setting in action

Sidewalk Labs proposes to launch a minimal set of digital services that would catalyze this ecosystem of urban innovation. These services and applications — all of which would be open to competition and subject to the pro- posed responsible data use process — represent innovations currently not being pursued by the market but that remain essential to achieving Waterfront Toronto’s quality-of-life objectives. (p. 378)

Conditions proposed by Sidewalk Labs to “catalyze” an urban innovation system (p. 380)

  • Shared digital infrastructure
  • Open and secure approach to architecture and standards (physical, data format, security and resilience, protocol, p. 381)
  • Digital services
  • Trusted process for responsible use (i.e., its proposed Responsible Data Use Guidelines and Assessments)

In what parts of the digital project would Sidewalk Labs participate? (pp. 380-381)

  • Core network – in other words, its role will be, to borrow a phrase, to build “the neighbourhood from the internet up”
  • Designing the standardized mounts
  • Various core digital for the aforementioned innovation streams (i.e., the chapters in this Volume)
  • Ubiquitous wi-fi
  • Software defined network
  • Super-passive optical network.

In short, it looks like Sidewalk Labs would be responsible for building the base platform and setting its standards.

Who would makes purchase decisions?

Procurement is a key issue. I have a feeling it’ll be addressed in Volume 3.

It’s all about surveillance “urban data”

It’s the provision of a ubiquitous surveillance network that will allow not only Sidewalk Labs, but other companies to develop “countless” other applications:

Sidewalk Labs believes the urban data generated by these services would catalyze third parties to create countless other applications to improve quality of life, along with the application-specific hardware designed to support them. (p. 383)

The IDEA District is a surveillance district. It is being designed to allow for ubiquitous surveillance. Any restrictions on surveillance will be interpreted by Sidewalk Labs as a restriction on the ability to increase quality of life. And also on their ability to make money, as suggested by the fact that they want to be compensated with bonus payments for not engaging in unfettered data sharing and data-based advertising.

Private governance: The Urban Data Trust

It would initially be a private entity that “could evolve into a public-sector or quasi-public agency over time.” (p. 383)

Next up, part two of the Urban Innovation chapter.

 

Posted in Quayside | Tagged , , , , , , , , | Comments Off on Liveblogging Sidewalk Labs’ Master Innovation and Development Plan, Entry 32: The MIDP Volume 2, The Innovations, Chapter 5: Digital Innovation, Introduction

Liveblogging Sidewalk Labs’ Master Innovation and Development Plan, Entry 31: The MIDP Volume 2, The Innovations, Chapter 4: Sustainability

Posted on August 19, 2019 by bhaggart
  • Phase 1: Design an advanced power grid
  • Phase 2: ???
  • Phase 3: Profit!

Previous Master Innovation and Development Plan liveblog entries and relevant documents available here 

Chapter 4: Sustainability (pp. 297-373)

Introduction (pp. 298-303)

I really don’t know anything about these areas in and of themselves, so here are a few questions about governance and financing.

  • The big question in this section is, how close to deployable are these technologies? What factors are shaping their deployment (e.g., return on investment, existing technological limitations)?
  • On finance, given the huge positive externalities from public utilities, does it make sense to turn their provision over to a private entity?
  • Related, what options are being taken off the table due to the need for Sidewalk Labs to receive a return on its investment?
  • In terms of public financing, the Eastern Waterfront is only a small part of Toronto. What is the business case for deploying scarce public resources here and not elsewhere?
  • Sidewalk Labs practices technological solutionism (i.e., they see every problem through the lens of technological solutions, usually provided by for-profit companies). What solutions are they missing? What alternatives are not on the table?

Also, a reminder that results reported in this chapter assume not only full deployment everywhere in their “IDEA District,” but that all the technologies, from mass timber skyscraper production to self-driving cars, will work perfectly and on time. Would Sidewalk Labs have the power to compel private entities to go along with their plans?

Part 1: Creating Low-Energy Buildings (pp. 304-313)

Goal 1: Deliver Passive House–inspired buildings (pp. 307-309)

Goal 2: Improve modelling through real-time metering (pp. 310-312)

Goal 3:  Use digital tools to tie energy outcomes to energy codes (p. 313)

Cometh the energy bureaucracy

Sidewalk Labs sells its energy-monitoring idea as a way to improve efficiency, and to tailor it to allow for differences in energy needs:

At the full scale of the IDEA District, with a large number of buildings, this tool could form the basis for a real-time energy code that adjusts dynamically for occupancy, tenant type, and weather to ensure fair and appropriate energy use regulation. (p. 313)

Like so much in this report, Sidewalk Labs is downplaying the huge amount of regulation and bureaucracy their supposedly “smart” solution would require. Allowing different energy targets for different uses would require regulations setting out different categories of housing, occupancy, individuals and occupations. It would then require decisions about what level of energy use constitutes “fair and appropriate.” Best of all, this is the type of thing that can make people/voters very, very angry.

If the goal of this project were to increase the regulatory burden, one would be hard-pressed to create a more-perfect system.

Part 2: Optimizing Building Energy Systems (pp. 314-323)

Goal 1: Create automated “Schedulers” for offices, homes, and building operators (pp. 316-323)

Part 3: Making Full Electrification Affordable (pp. 324-333)

Goal 1: Design an advanced power grid (pp. 326-329)

You have to admire the cojones a planning document where “Design an advanced power grid” gets two-and-a-half pages of text (four overall, one of which is a full-page pull quote), while the plan to design a programmable thermostat gets almost five pages of text and eight pages total.

The take-away: Creating a series of smart thermostats is exactly twice as difficult as designing an advanced power grid.

Goal 2: Implement an innovative “monthly budget” bill target (pp. 330-333)

I’m not sure how well “dynamic hourly rates” (read: Uber-style surge pricing) for electricity will go over with Quayside residence.

This type of “innovation” raises another point I haven’t seen mentioned elsewhere, namely that it assumes that it can get away with treating Quayside/Waterfront/whatever residents differently from other Torontonians.

And I don’t mean this in terms of the extra conveniences and cool factor touted by Sidewalk Labs. Let’s not forget that for all the talk of Quayside having timber buildings and “raincoats,” for most of the next decade, should this all come to pass, the whole area will be a construction zone. Moreover, you can bet that the first several iterations of these new technologies are going to be as glitchy as hell, particularly since Sidewalk Labs will do their best to rush these products to market. That’s just how Silicon Valley rolls.

Also, living in this new neighbourhood is going to be expensive. Sidewalk Labs’ biggest idea for how to fund all these new bureaucracies and infrastructure is user fees and new taxes.

The big question is, how will this extra tax burden (and it doesn’t matter whether you call them user fees or taxes, residents will be paying them) and living in a construction site amid beta-tested technologies affect demand for Quayside/whatever units?

Basic economic reasoning would suggest that these factors would all depress demand for these units, as well as the prices they can command. This effect will be proportionate to the extent to which other Toronto housing units are seen as a substitute for Quayside/whatever units: The more that Torontonians treat Quayside like any other neighbourhood, the more pronounced this depressed demand/prices would be.

And while Sidewalk Labs is obviously counting on Quayside/etc. shininess and novelty to drive demand, there’s also the possibility/likelihood that these extra costs and inconveniences (especially in the short run), combined with its coveted light-rail link will lead Torontoinans to want to visit Quayside occasionally rather than live there. Rail links work both ways.

My point here is that these type of less-than-rosy scenarios, which arewell within the realm of the possible, are nowhere even hinted at in Sidewalk Labs’ Panglossian proposal. Neither is it in the urbanMetrics report, which merely ran the numbers that Sidewalk Labs gave it. I saw no discussion of substitution effects in urbanMetrics’ report. As far as I can tell, Sidewalk Labs provided the company with “Development figures (i.e. total floor area estimates, detailed allocations by land use) and subsequent supporting assumptions (i.e. population, employment, construction costs, development timing and phasing etc.),” which they assume are accurate (Economic Impact Analysis, p. 43). Sidewalk Labs has not, as far as I can find or recall, in its nearly 1,500-page report, provided any reasoning regarding how it arrived at these figures.

Maybe the information is buried in an appendix?

Tinier-than-Toronto-average apartments (if the law is changed to allow them), a decade-long construction zone and a uniquely high tax burden could all depress demand for this project.

Quick note on urban innovation

Sidewalk Labs’ entire pitch is built around the idea that there isn’t enough “innovation” in urban infrastructure, but there’s a very good reason for that. Glitchy websites are an inconvenience; glitchy buildings or traffic signals can get people killed.

Plus, residents are stuck in their cities; it’s hard to just up and move somewhere else when the entire system goes offline and you can’t even get into your house. I’m old enough to remember Vancouver’s “leaky condo” crisis. I recall the barely controlled fury of Vancouver residents appearing before the House Finance Committee to ask for some kind of relief. It was a fury born of the reality that, having sunk a significant portion of their life’s savings into a lemon of a primary residence, they were stuck in a kind of living nightmare.

Now imagine Quayside residents’ reactions the first time the trash pipes break. You can bet that even if Sidewalk Labs and Waterfront Toronto are directly responsible for the district, elected municipal, provincial and federal politicians will catch holy hell for whatever goes wrong.

Sidewalk Labs is pushing the best-case scenario, but it’s vital to remember that not all innovations work out. Being a guinea pig is great when you’re getting treats; it’s not so great when you’re the rodent being force fed the drug with the unexpected side effect. And when urban innovations don’t work out, they can turn one’s life into a living hell overnight. Sometimes conservatism and caution – the principles baked into our zoning bylaws – are good things.

Part 4: Using Clean Energy to Heat and Cool Buildings (p. 334-343)

Goal 1: Design a thermal grid to distribute clean energy (pp. 336-339)

Sure, why not?  #notmyfield

I would, however, like an independent assessment of their proposal as outlined in Appendix document “Thermal Energy Grid: Phase 2 report,” please.

The big question is, who can provide this assessment? Waterfront Toronto can’t; the Plan Development Agreement places them in a clear conflict of interest. (Yet another reason why this entire project is fundamentally flawed.) City of Toronto, it’s up to you.

Goal 2: Capture building “waste” heat, geothermal energy, wastewater heat, and other clean energy source (pp. 340-343)

Same demand as above. Also, these proposals assume that it can be expanded over the entire “IDEA District.” But what happens if not everyone (e.g., the privately owned Keating land) wants to play ball? After all, even Sidewalk Labs isn’t proposing that it should be able to expropriate other people’s land.

Part 5: Reducing Waste and Improving Recycling (pp. 344-357)

I’ve dealt with this issue in a previous post, and it’s #notmyfield, so I’ll leave it to others, except for a few comments (see below).

Goal 1: Improve waste sorting through responsive digital signage (pp. 346-349)

Goal 2: Implement “pay-as-you-throw” smart waste chutes (pp. 350-351)

New tax alert: Again, another tax on a small subsection of Toronto residents that won’t be paid by apartment dwellers elsewhere in the city. Key issue: how will this tax affect demand for these properties.

Goal 3: Reduce contamination during removal with vacuum tubes (pp. 352-353)

Goal 4: Convert organic waste into clean energy (pp. 354-357)

Part 6: Managing Stormwater Naturally and Actively (pp. 358-365)

Another Waterfront district-level-only plan.

New bureaucracy alert: It would be up to the Open Space Alliance, which as Dr. Natasha Tusikov points out, has a ridiculously expansive mandate, to “operate and maintain the stormwater system.” (p. 359)

Goal 1: Design green infrastructure into a neighbourhood (p. 360-361)

Goal 2: Monitor stormwater levels and quality with digital tools (p. 362-365)

Public Engagement (pp. 366-371)

In which public engagement as it relates to sustainability is discussed, and I am reminded again that Sidewalk Labs provides no list of the events it has held or the public members of its various panels.

And that’s our show for today.

Posted in Quayside, Uncategorized | Tagged , , , , , , , , | Comments Off on Liveblogging Sidewalk Labs’ Master Innovation and Development Plan, Entry 31: The MIDP Volume 2, The Innovations, Chapter 4: Sustainability

Liveblogging Sidewalk Labs’ Master Innovation and Development Plan, Entry 30: The MIDP Volume 2, The Innovations, Chapter 3: Buildings and Housing

Posted on August 18, 2019 by bhaggart

In which I start off thinking I won’t have anything to say and end up writing a lot. Also, on the desirability, or lack thereof, of super-tiny, totally “livable” studio apartments. And! The economist in me has something to say about rent caps.

Previous Master Innovation and Development Plan liveblog entries and relevant documents available here

Chapter 3: Buildings and Housing (pp. 202-293)

Introduction (p. 204-207)

Part 1: Accelerating Construction Timelines (pp. 208-235)

…through the use of an unproven technology (“mass timber” for 30-storey buildings) and precut buildings. (p. 205). Which would make property more valuable, leading to higher taxes, which could be funnelled into affordable housing. (p. 205)

Sidewalk Labs identifies customized buildings and costly steel and concrete as the enemy (high costs for design). The solution: cookie-cutter buildings made out of wood. (p. 208)

Question: How would Sidewalk Labs be involved in the supply chain? (e.g., p. 209 comment)

Goal 1: Catalyze a new sustainable industry around mass timber (pp. 210-219)

Another reminder that this proposals projections are based on best-case scenarios: “Using wood for all 2.6 million square feet of building development in Quayside would be equivalent to removing over 20,000 cars from the road annually.” (p. 210, emphasis added)

Two pages on “Ensuring fire resistance with ‘Shikkui plaster’” (pp. 214-215).

I’m a bit unclear about the status of this technology. Is it ready to go? What still needs to be done to prepare it for mass distribution and use?

Durability?

This may be a bit out of the blue, but this section reminded me of a friend from undergrad whose family was in construction. New homes, he said, were designed to last just over two “generations”: they’ll start to fall apart after they’ve been sold twice (e.g., about 40 or so years I think). How long are these buildings supposed to last? I didn’t see anything in here about that.

Goal 2: Launch a factory to produce a complete library of building parts (pp. 220-232)

Regulation change: Sidewalk Labs wants to speed up regulatory approvals by getting the various cookie-cutter building pieces pre-approved, rather than, I’m guessing, the regulator/city approving the final project. (p. 22)

Sidewalk Labs promises “unique designs” based on a selection of pre-set “parts.” (p. 220)

A driver of affordable housing (we pass the savings on to you!): “By injecting more certainty into the building process, Sidewalk Labs hopes to enable projects that meet both the city’s objectives for affordability and the waterfront’s standards for aesthetic excellence.” (p. 221).

Descriptions of the parts are on pages 222-223. Architects’ vision exercises on pages 224-225. This is beyond my expertise. Engineers and architects: Do these plans make sense?

Do these numbers make sense?

I’d feel a lot more comfortable about the solidity of Sidewalk Labs’ plans if this sentence were a lot less conditional:

Sidewalk Labs believes the structural assembly of a building could ultimately reach speeds of one floor a day, compared with a typical on-site construction timeline of one floor per week. (p. 227, emphasis added)

As far as I can tell, their big, oft-repeated claim that they can complete projects 35% faster than today’s standard is based on this guess – no citations provided in the report:

To complete a 12-storey building — which involves basic structural assembly as well as the installation of all finishes, the connection of all electromechanical equipment, and the execution of all tests — Sidewalk Labs estimates that its facto-ry-based process can reduce construction time from 20 months to 13 months, delivering projects 35 percent faster than today’s methods. (p. 227)

Goal 3: Coordinate the supply chain with a digital delivery system (pp. 233-235)

Proposed: A “Sidewalk Digital Fabrication system” to track the entire production process, from timber to building creation. (p. 234).

Sidewalk Labs would control the supply and value chain

Ah, here we go. In answer to my above question, Sidewalk Labs would “build the underlying infrastructure to support this advance system,” outsourcing some parts to other companies. (p. 234)

So: Ontario labour, Sidewalk Labs-run mill (?), Sidewalk Labs-controlled value chain?

And would the building parts be patented? Who would control the IP in them?

Part 2: Helping Neighbourhoods and Households Evolve (pp. 236-261)

The dream

Within a single neighbourhood people could find affordable space to pursue their professional dreams, whether a single co-working desk to plot out a startup or a short-term stall to sell a hand-crafted confection. Homes could meet the needs of growing families and single-person households alike. (p. 236)

I’m really trying not to be churlish when I ask this, but doesn’t this describe a lot of downtown Toronto already?

Smaller – sorry, cozy – apartments equals more (affordable) units

an efficient approach to unit design would enable developers to create more overall units while retaining liveability, unlocking new value that could help meet the ambitious goals of affordable and below-market housing programs. (p. 237)

Goal 1: Create an adaptable “Loft” space built for all uses (pp. 238-245)

New regulation alert: “Sidewalk Labs plans to implement minimum targets on its Loft spaces for commercial usage, so they always reflect some level of mixture across commercial and residential uses.”

In other words, Sidewalk Labs wants to set bylaws for commercial and non-commercial building usage.

Huge savings mentioned on page 242. Again, would these designs work? Are they allowed under current bylaws? If not, why not? #notmyfield [Spoilers: I don’t think their proposals are currently street legal.]

Goal 2: Accelerate renovations with a flexible interior wall system (pp. 246-250)

Again, #notmyfield, so I have no idea how well this type of system would work, although I keep coming back to the thought that Sidewalk Labs got this job because they’re a Google company, and they don’t have any expertise in these types of issues. Expertise welcome…

Goal 3: Enable a safe, vibrant mix of uses with real- time building codes (pp. 251-252)

Ah, the real-time building code, which is zoned for specific, measurable variables and not land uses (building uses, not prescribed land uses? (p. 251)). Urban governance experts: can zoning bylaws be reconstructed in this way? What would be lost in doing so (Sidewalk Labs has already told us what would be gained)?

Question: What would the surveillance impacts of this surveillance network be?

I’d also like to see the worst-case scenarios of mixing industry/commercial with residential. A mom-and-pop craft jeweller (p. 252) seems pretty innocuous, but I’m betting that creative readers can imagine worse-case scenarios.

Still, it’s weird that Sidewalk Labs’ innovative vision involves something that reminds me of the tenement housing in New York from over a century ago. Those buildings were also mixed-use. But, again, this is an area I don’t know much about. Enlightenment welcome!

And just in common-sense mode, I’m not sure I’d put “restaurants” and “single-dwelling units” in a “use-neutral” category. Not sure I’d want to live above, say, a 24-hour diner.

Goal 4: Design affordable and flexible housing units (pp. 253-261)

Let’s get small

“micro-units” (smaller units that rent for less while remaining livable through efficient design) and co-living programs (which feature shared building amenities, such as communal kitchens, to enhance community while keeping rents lower). (p. 253)

This proposal would irk me a lot less if they weren’t trying to sell us on housing built around always having roommates and shared kitchen as an opportunity “to enhance community.” This was obviously written by someone who has never lived with other people. More likely, they’re suppressing a traumatic memory of the skanky refrigerators that everyone who has ever had a roommate has had to deal with.

Also, my first solo apartment – Bathurst and Harbord, as it happens – was smaller than many hotel bathrooms. It was designed for efficiency. It also couldn’t accommodate more than three people at any time. It was “liveable,” and my landlord was fantastic (shoutout to Carlos! Best landlord in Toronto), but I wouldn’t go overboard selling it as a fantastic solution for modern living.

Tone that pitch down, Don Draper.

Also, (and please note that I’m writing this in real time) I’m assuming that the reason these types of apartments are innovative is because they’re currently not allowed under existing bylaws? Would any existing rules have to change (and why are these rules there in the first place)? Or am I just being cynical? Again, #notmyfield.

Finally, “free in-building storage”? (p. 255) I’ll be my remaining shred of sanity that this would be included in the condo fees or rental price.

More oversell

Sidewalk Labs’ approach to public realm design is also meant to improve comfort for residents in efficient units. An expanded set of parks, plazas, and public spaces — comfortable year-round thanks to weather-mitigation systems— means people could spend more time outdoors, in spaces they can decide how to use themselves. (p. 259)

Speaking from experience, these outdoor won’t make up for apartments described as “liveable.”

Burying the lede

Answers! It turns out that the reason Sidewalk Labs’ proposals for building apartments that qualify as “liveable” is they’re currently not allowed:

Sidewalk Labs proposes to seek relief from existing relevant guidelines and standards related to unit size to enable developers in the project area to create these new occupancy types within the IDEA District. (p. 259)

I’m pretty sure that my bathroom-sized apartment was legal in 1996 (my landlord was very conscientious). There’s a very good reason that smaller apartments aren’t currently legal: it would be like living in a pod.

Sorry, I meant “affordability by design” (p. 260). Or, as it’s also known, “currently illegal.”

So, there you go. Sidewalk Labs can only deliver the goods if it implements building designs that are not allowed under the law as it stands. Couldn’t it have tried to stay within existing building codes, just a teensy bit? I guess that’s what makes them #innovators.

Part 3: Expanding Tools for Housing Affordability (pp. 262-287)

Or, as they’re also known, “‘liveable’ pods based on not-currently-allowable designs”

Sidewalk Labs proposes to create new types of units designed with affordability in mind from the start. (p. 263)

Goal 1: Create an ambitious program to meet the housing affordability challenge (pp. 269-277)

I’m not sure this sounds as impressive as you think it sounds

Sidewalk Labs commits to achieving this program mix in Quayside using a combination of existing government funding sources and new innovations. (p. 269)

Read as: Spending public money already earmarked for affordable housing and proposing a housing project that’s not allowed under current rules.

Rental caps: An evidence-free proposal

New regulation:

In Quayside, to ensure these units remain affordable for middle-income families, Sidewalk Labs plans to implement a rent cap. For example, rents for a two-bedroom unit would range from $1,492 to $2,238, according to existing rental bands established by the city. (p. 272)

Hm. If I were feeling more energetic, over 1,000 pages into this report, I’d link to the research showing something that every MA economics student is taught, which is that rent-controlled apartments (which is what this is) tend to paradoxically reduce the availability of affordable housing. At the very least, Sidewalk Labs needed to engage with this analysis. But that would’ve required the preparation of an actual report, and not a sales brochure.

Oh, fine. Here’s a Brookings report (centrist US think tank) that raises several issues with rent control. And here’s one from the Urban Institute (US) synthesizing research on rent control. tl;dr: Both suggest positive benefits for those in the rent-controlled apartments, and mixed results (often negative) for the community as a whole.

Here’s how I found them: I Googled them. Took me three seconds: Two to sigh and roll my eyes in frustration for having to put in more work to evaluating something that reads like it was assembled by a public-relations committee than the person who wrote it, and one to do the typing (I’m a fast typer).

Try it yourself: “effect of rent controls on affordable housing.” Skip the Google-featured shapeillinois.com result, which seems to be from a front for the US apartment building industry. There’s loads of stuff here.

To be clear, it’s fine to include this idea in a development plan, but you have to give it some context to show why it’s a good idea, especially since any economist would immediately be skeptical of it. As it stands, there’s nothing here to suggest why this idea would work, which makes it look like a promise that is easily made and poorly researched.

Goal 2: Achieve this program with innovation that yields greater affordability (pp. 278-287)

Where would the savings come from?

  1. Affordability by design (i.e., currently illegal designs for “liveable” apartments)
  2. “factory-based” timber construction
  3. New tax alert: condo resale fees. (p. 278)

And most of the funding comes from “factory-driven land value” (p. 279) – i.e., this bet on mass-produced timber buildings better work out.

Quayside would pony up $77 million to catalyze funding sources.

New bureaucracy alert: “a proposed housing trust,” one of whose jobs would be to “package some of these new funding sources to meet affordability objectives” (p. 280). So it would need some finance experience, in addition to (presumably) being a landlord.

You can’t keep a good number down

That 35% claim shows up again (p. 282). It would be interesting to search the report to see how many times each such claim is repeated.

Condo resale fee

Question: Quayside/Waterfront cannot be viewed in isolation from the rest of the Toronto condo market. How would an extra resale fee affect the entire market, including demand for Quayside condos? If I had to bet, I’d guess that it would depress the overall price of Quayside condos by about 1%. But of course there’s no such analysis mentioned here that I could see. Such an analysis would attempt an estimate at the total extra fees a Quayside resident would have to pay compared with other Torontonians.

Waterfront Housing Trust (p. 285)

Ah, here we go. The Waterfront Housing Trust would administer a “housing trust fund: a new financial vehicle to assemble and disburse funding for below-market housing across the Sidewalk Toronto project area.”

It “could assemble funding from a variety of public and private sources and “lock-box” this funding for below-market housing within the IDEA District … .” As well as “alternative funding sources.”

It would “provide capital grants and other financial support for developers, both private and not-for-profit, seeking to meet significant affordability commitments.”

Again, as I’ve said so many times by now, the word “could” is a hint that this is an idea, not a plan. It should be analyzed as such. This is not a substantive proposal.

Public Engagement (pp. 288-293)

In which public engagement is summarized on building and housing issues. And in which I’m reminded again that we don’t know the names of the people on Sidewalk Labs’ various panels, or have a complete list of all the meetings (public and private) they’ve held.

Bonus: I read the endnotes

Another reminder that this project assumes total success. And then some:

Unless otherwise noted, all calculations that refer to the full proposed IDEA District scale are inclusive of the entirety of its proposed geography, including all currently privately held parcels (such as Keating West). (p. 294)

That would be the Keating West that is otherwise excluded from Sidewalk Labs’ plans (it’s in private hands).

Phrased differently: While the report notes in other places that outside of Villiers West and Quayside, private owners would be invited to participate in these plans, the figures in this Chapter assume that everyone gets on board.

My recommendation: Pick a number and discount all of Sidewalk Labs’ predictions by that amount. There’s no way that it will hit these targets. Nothing every goes exactly according to plan. Readers would do well not to take this plan’s claims at face value.

Posted in Quayside | Tagged , , , , , , , , | Comments Off on Liveblogging Sidewalk Labs’ Master Innovation and Development Plan, Entry 30: The MIDP Volume 2, The Innovations, Chapter 3: Buildings and Housing

Liveblogging Sidewalk Labs’ Master Innovation and Development Plan, Entry 29: The MIDP Volume 2, The Innovations, Chapter 2: Public Realm

Posted on August 17, 2019 by bhaggart

Previous Master Innovation and Development Plan liveblog entries and relevant documents available here

The next few posts are going to be a bit threadbare, because what more needs to be said? At least for now.

Chapter 2: Public Realm (pp. 118-149)

Introduction (pp. 120-125)

Part 1: Creating More Open Space (pp. 126-149)

Goal 1: Reclaim space for the people (pp. 128-139)

Street design favouring pedestrians. Modular pavement.

Goal 2: Make the most of new parks, plazas, and open spaces (pp. 140-149

Part 2: Making Open Space More Usable More of the Time (p. 150-177)

Goal 1: Reinvent the role of the ground floor (pp. 151-166)

Flexible leasing tools (read: apps and financing), adaptable building structures (p. 150)

Goal 2: Design an outdoor comfort system for all seasons (pp. 167-177)

Based on “real-time climate data and a set of deployable weather-mitgatin fixtures – such as retractable awnings and inflatable shelters.” (p. 150)

Talk about “developing a system that proactively predicts and plans for outdoor comfort” (p. 169). At the full-scale prototype phase. (p. 170)

Part 3: Ensuring Open Space Is More Responsive (pp. 178—191)

New bureaucracy alert:

The proposed OSA would administer shared physical infrastructure. … The proposed entity could also help urban innovators, ranging from civic technologists to startups, run pilots in open space. (p. 178)

Goal 1: Establish an entity to coordinate programming, operations, and maintenance (pp. 179-181)

The Open Space Alliance: Coordinate programming, operations, and maintenance. (p. 179)

Issue: Toronto faces chronic funding shortages.

The OSA would be responsible for a lot of space that was previously vehicular rights-of-way, which would be operated more like parks but “still owned by the city and managed by its transportation department, but it would now be operated more like parks.”

These spaces would need to be effectively integrated with the local park network and would benefit from comparable levels of management and funding.

Question: how much funding would it need?

It would be a public-private partnership “jointly governed and financed by both sectors.”

All city-owned open spaces would remain owned by the government, which would participate in programming, operations, and maintenance with the OSA.

Questions:

  • What would be the anticipated government/taxpayer contribution?
  • How much more would Torontonians have to pay for this bureaucracy?
  • How much would private sector be expected to pay?
  • How do you guarantee sufficient resources?

This is an odd principle

The public realm needs to reflect a truly public space — with the city retaining ownership of city-owned open spaces — while also protecting the needs and rights of private property owners on their land. (p. 181)

Why is this statement, emphasizing the sanctity of private property owners here? It seems to be responding to an unstated specific concern.

And who decides what counts as an improvement of an open space?

This would seem to be much more controversial than it’s portrayed as being:

Generally, the OSA should be set up to facilitate the ideas of others who want to activate and improve open space, rather than act as a top-down planning body. (p. 181)

Goal 2: Provide physical infrastructure that enables community programming

What billions of dollars and giving up governance control over a significant part of the waterfront gets you

There are a lot of coulds in this pitch for something that kind of underwhelms:

A teenager could join a virtual queue to play a life-size chess game projected onto the side of a building. The next day, the projected game could be Chinese checkers, and an elderly resident might sign up. Crowds could gather to watch the game in action. (p. 182)

Crowds could, but how likely would this be?

Everyday surveillance: What could go wrong?

With [the app] CommonSpace, park operators or community organizers can enter information they observe about public life into a user-friendly app, such as what assets or areas people prefer or what spaces they avoid. (p. 185)

Fun fact: The word “surveillance” appears twice in the entire main text of the MIDP (p. 1196 and p. 1220 of the consolidated MIDP). It also shows up once in the footnotes, in the title of a report. The cynic inside of me thinks that this was two times more than was intended.

Goal 3: Provide digital infrastructure that enables proactive maintenance (pp. 186-189)

Of utilities and infrastructure.

Goal 4: Connect urban innovators and public spaces (pp. 190-191)

Why is Sidewalk Labs talking about its proposed Open Space Alliance as if it already exists?

The OSA’s new policy and funding framework, which encourages experimentation, coupled with the shared physical and digital infrastructure described on Page 184, enables urban innovators, from civic technologists to businesses, to prototype their ideas in a real-world environment. (p. 190)

For the record, the OSA proposal suffers from almost all of the problems of the proposed WTMA, absent the trigovernmental steering group. No costing, no sense of number of employees. It’s a notion, not a plan. If this is the best Sidewalk Labs can do after 18 months, they can’t be trusted to manage a project like this.

Public Engagement (pp. 192-199)

Feedback on public-realm aspects of Sidewalk Labs’ proposals.

Posted in Quayside | Tagged , , , , , , , , | Comments Off on Liveblogging Sidewalk Labs’ Master Innovation and Development Plan, Entry 29: The MIDP Volume 2, The Innovations, Chapter 2: Public Realm

Liveblogging Sidewalk Labs’ Master Innovation and Development Plan, Entry 28: The MIDP Volume 2, The Innovations, Chapter 1: Mobility, Parts 5-6

Posted on August 16, 2019 by bhaggart

In which the MIDP finally pushes me over the edge and I unexpectedly reach the point where I’d read enough to render a verdict on the entire report.

Previous Master Innovation and Development Plan liveblog entries and relevant documents available here

I really didn’t think it would be the mobility section that finally sent me over the edge.

Part 5: Improving Mobility Management (pp. 84-91)

Goal 1: Establish a new entity to coordinate the entire mobility system (pp. 86-88)

New bureaucracy alert: The Waterfront Transportation Management Association (WTMA) would be responsible for coordinating “the transportation system in the IDEA district by deploying a mobility management system.” (pp. 84-85) It would not have much of an effect at the Quayside level. (p. 85)

Its roles:

  • Creating a mobility subscription package
  • Deploying a holistic mobility management system
  • Managing and setting prices for the curbside and parking systems
  • Procuring and operating new technologies, such as adaptive traffic signals, dynamic pavement, freight and deliveries, or other third-party systems and apps
  • Integrating systems with third-party navigation apps
  • Allocating space across the needs of mobility, access, safety, and the public realm
  • Reporting on performance targets related to congestion, mode share, and customer service (p. 86)

Financing:

  • Financing: should be self-sustaining.
  • Suggested financing sources: many, many types of fees for using mobility services in the District, and “charges for mobility services to residents and employees.”

This listing of responsibilities and some vague thoughts on financing, again, is not a plan; it’s an idea, a notion. These proposed funding suggestions are just kind of thrown out there, the report version of spitballing. Whether they would end up being sufficient is left unexamined, in what seems to be a particularly half-baked proposal (How many people would be required to run this entity? Are they unionized? How much would this all cost? How much money would be required for it to be “self-sustaining”?).

Also, why is the Eastern Waterfront a sufficient scale for this administrative agency, which is being asked to do a whole lot of specialized work? That the Eastern Waterfront just happens to be the right scale for a WTMA seems awfully convenient, especially since Sidewalk Labs would effectively be creating a new agency for what is – let’s not forget – a pretty small piece of land in the context of Toronto itself.

Moving on (ha), what would this vague notion of an agency do?

Develop specific guidelines (p. 87);

  • “Oversee planning, operations and maintenance” of all roads, hardware and software for parking, curb and traffic management
  • Set and enforce parking, curbside and road usage fees
  • Set speed limits
  • Manage street closures for construction or events
  • Handle data properly
  • Create that trip-planning interface/app Sidewalk Labs is all keen for
  • Snow and debris clearing “beyond heated pavement”
  • Constructing and financing roads or parking facilities.
  • Run the “advanced mobility management system”

Those are a hell of a lot of responsibilities. It will involve workers that had to do both physical labour and maintain complex IT systems, systems that are much, much more complex than anything Toronto has today, in part because everything is interconnected.

And yet Sidewalk Labs throws all this out there without any attempt to cost it out, or to explain exactly who (in terms of actual people) is going to do this work.

If you look closely, you can actually pinpoint the exact moment where my brain breaks

I’ve been trying to keep my writing breezy and loose, in part to keep my interest up in what has become a very long slog, but I’ve also been trying to keep my objectivity about what Sidewalk Labs is proposing. When I began reading the MIDP, I had a lot of reasons to doubt the quality of this project, many of which I’ve detailed over several posts, but I really did try to keep in mind that I could be wrong. Change isn’t necessarily bad.

But this section finally broke me. To cavalierly propose what would almost certainly end up being a multi-million-dollar agency to govern a couple hundred acres, without even trying to cost out the proposal, or to think through how it would be staffed… it’s a joke.

Sidewalk Labs was supposed to present a plan. A plan implies an idea about what you will do, and how you will do it. It implies details. And we get … this?

The WTMA is not a serious proposal. It is a repository for all the things that need to happen for their Rube Goldberg-esque plan to work.

The MIDP is not a serious document. It’s a sales job put out by company that will say anything to get this project across the finish line. It scatters information about its various components throughout the document. Sidewalk Labs sees the WTMA as a subsidiary part of an overarching administrative body, which may or may not be Waterfront Toronto, but whose capacities in any case do not currently exist.

And we get this information stated clearly only in Volume 3 (page 70), 1,320 pages into the MIDP and 456 pages beyond this section, which should have been the comprehensive discussion of this organization.

And that list above, of what the WTMA would do? Notice how it includes “Manage street closures for construction or events”? Well, here’s what Sidewalk Labs writes on page 11 of “Mobility Technical Appendix F: Mobility Management” – that’s right, Sidewalk Labs, someone is reading your appendices, even though they’re not included with the main report:

The WTMA is not envisioned to do the following things … Manage street closures —to be done by Transportation Services… . (emphasis added because, just, wow)

So, like, whatever. Part of me – the professional part that’s offended by the half-assedness of a report that could win the company that produced it company billions of dollars and some of the most valuable undeveloped real estate in North America – cannot believe how incompetent Sidewalk Labs is at what should be its specialties: keeping their story straight and putting their best foot forward.

The researcher part of me, however, is not surprised. This type of clumsiness and lack of attention to detail has characterized Sidewalk Labs’ Toronto adventure from the very beginning, from the early insistence that a YMCA day camp counts as consultation to the fast-and-loose way they’ve played with data governance.

Welcome to gridlock, population Sidewalk Labs

Oh! And just to show that Sidewalk Labs is truly not serious about this proposal, the WTMA – not the overarching authority, but the agency responsible for plowing the roads, maintaining the software, closing off roads for block parties and collecting fees “would include a steering committee with representatives from all three orders of government” (Volume 3, p. 70).

WHY???? Why saddle such an entity with this type of governance? As the Auditor General’s report makes clear, it’s this tripartite decision-making capability that has hampered Waterfront Toronto’s mission to develop the waterfront. And Sidewalk Labs wants to duplicate this dysfunction AT THE OPERATIONAL LEVEL?

It makes no sense whatsoever. If you’re going to continue to have tripartite responsibility for this area, you keep it at the policy level, with line agencies disposing of the policy-level’s proposals. Stupid dumb.

What makes this proposal even worse, is this silly nod toward a tripartite steering committee represents the extent of Sidewalk Labs’ discussion of this multi-million-dollar entity. That’s it.

It’s irresponsible. It’s ridiculous.

This idiotic WTMA proposal has all the hallmarks of a proposal made by an organization that is making this stuff up as they go along, that is willing to say anything to get their project across the finish line, hoping that nobody reads their convoluted, overlong and repetitive, index-free proposal too closely.

Rendering a verdict

This WTMA proposal exposes the MIDP for what it is: a cynical scheme that disrespects the many Torontonians who take the development of their waterfront seriously and only want the best for their city.

Very Serious Torontonians can pretend that this proposal is anything other than a poorly conceived land and power grab by Sidewalk Labs and Google, but the rest of us are under no obligation to take this charade seriously.

This project may very well come to pass, via a process that has been marred by irregularities from the very beginning. But that won’t change the fact that this is a poorly thought out proposal not worthy of serious consideration. If implemented, Toronto will rue the day Will Fleissig and Waterfront Toronto invited Google to town.

I’m out. At this point, 871 pages into this repetitive monstrosity, there’s very little left to learn. I’m going to continue to analyze the MIDP, and I may do another post on Waterfront Toronto’s Note to Reader, and a final summary post, but I’ve read more than enough to come to a conclusion about whether the MIDP is a sound proposal.

It’s not.

I began writing this series in order to understand Sidewalk Labs Master Innovation and Development Plan, and now I do: There is no plan; there is only a sales pitch.

The Emperor has no clothes. There is no need to pretend otherwise.

Goal 2: Deploy a real- time mobility management system (pp. 89-91)

Part 6: Designing People-First Streets (pp. 92-107)

Goal 1: Create four new types of streets to move people and make places (pp. 96-107)

Public Engagement (pp. 108-115)

Discusses feedback from the public. As with the other mentions of public engagement in this Volume, we can’t see whether the selected views are representative. At least one Reference Panel member suggests that this feedback is not representative and the product of a tightly managed process.

Posted in Quayside | Tagged , , , , , , , , | Comments Off on Liveblogging Sidewalk Labs’ Master Innovation and Development Plan, Entry 28: The MIDP Volume 2, The Innovations, Chapter 1: Mobility, Parts 5-6