Manage implementation: Difference between revisions
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 51: | Line 51: | ||
The [[Living_Labs/1|Vienna lab]] went the other way entirely. Instead of building, it reactivated an underused space in Liesing as a flexible activity hub, with cultural and food offers, and invited residents and local initiatives to help shape and run it, recruiting the people behind the offers through a neighbourhood platform they already used. Next to it stood a temporary bike-sharing station that needed no docking infrastructure at all, since it worked as a designated area inside the city's existing mobility app. The whole thing was set up and operating across roughly six weeks of one summer ([[Publications/6|Deliverable 6.1]]). | The [[Living_Labs/1|Vienna lab]] went the other way entirely. Instead of building, it reactivated an underused space in Liesing as a flexible activity hub, with cultural and food offers, and invited residents and local initiatives to help shape and run it, recruiting the people behind the offers through a neighbourhood platform they already used. Next to it stood a temporary bike-sharing station that needed no docking infrastructure at all, since it worked as a designated area inside the city's existing mobility app. The whole thing was set up and operating across roughly six weeks of one summer ([[Publications/6|Deliverable 6.1]]). | ||
Neither route is the better one. They | Neither route is the better one. They suit different stages in the life of a measure. | ||
The question to settle before delivery starts is which measures in your package you are confident enough to build outright, and which ones should be tried in a reversible form first while the capital is still uncommitted. | |||
<div class="sump-versus"> | <div class="sump-versus"> | ||
| Line 65: | Line 66: | ||
</div> | </div> | ||
</div> | </div> | ||
== Record it while it happens == | == Record it while it happens == | ||
Latest revision as of 10:07, 19 October 2026
Step 10 of 12 Implementation & Monitoring
Phase four is where the plan stops being a document. The measures adopted in the previous step now have to be detailed, contracted, built and switched on, by departments and organisations that each hold one piece of the work. SUMP asks for two things here. The responsible bodies plan the technical detail of their own projects and procure whatever has to be bought, and somebody coordinates the whole programme so that the pieces arrive in an order that works. In the outskirts the second is the difficult one because the pieces belong to different employers and the slowest of them sets the pace for everyone.
The critical path is not the construction
Putting a public bike-share into an outer district of Budapest meant running two tracks in parallel for well over a year before anything appeared on a street. One track was the service. The district authority, the city transport authority, the national transport research institute and the university worked through legal requirements, then folded the pilot area into the city's own next-generation bike-share framework, then negotiated and signed a service contract. The other track was the stations. Macro-level siting, then detailed micro-siting, then a contract with one firm for the civil engineering design, then permits and construction planning, then authorisations from the district, the transport authority and the city roads body, then a second contract with a second firm to build them. Construction itself took the last quarter of the programme.
Two things in that account are worth taking seriously. The first is the proportion. Almost all of the elapsed time went on legal work, siting, permissions and contracting, and the visible part, putting stations in the ground, was the short bit at the end (Deliverable 5.1). A delivery plan that schedules the construction carefully and treats the permissions as an administrative preliminary has the wrong shape and will slip.
The second is what happened to the timing. The launch depended on the readiness of the citywide bike-share extension, which a different organisation was rolling out, and when that slipped the lab's operating period was cut from six months to three. The content of the pilot survived intact. What suffered was the comparison because a shortened window changes which season the service is judged in (the Budapest lab's own account). That is the characteristic shape of a periphery delay. The measure still gets delivered, and the cost of the delay lands on the evidence rather than on the thing itself.
Name the dependencies you do not controlWrite down, for each measure, every event outside your own administration that has to happen first. A neighbouring authority's tender cycle, a utility's works, a permit from a roads body, another organisation's system launch, an operator's concession renewal. Give each one an owner inside your programme whose only job is to ask about it regularly, and agree now what you will do if it moves, including whether the measurement window moves with it. A dependency that nobody is watching is not a risk you have accepted, it is one you have not noticed.
Procurement decides what you actually get
Most of what a mobility plan promises in the outskirts is a service somebody else operates, so the contract is the measure. The DREAMS review of shared mobility governance is blunt about what goes wrong. Operators do not always honour what they agreed, whether that is the number of vehicles kept in an area or the transmission of operating data, and they tend to drift back towards the dense parts of their territory. Checking compliance costs the authority staff time, and without penalties there is little reason for an operator to prefer the thin area. The free-floating market in particular is volatile, with operators arriving, merging, withdrawing and failing, which matters most in sparsely populated areas where profitability was uncertain to begin with (Deliverable 2.2).
Four things follow for the specification. Write the service level as something observable in your area rather than as a fleet total, since vehicles registered to a city are not vehicles available in an outskirt. Make data transmission an obligation with a named format and frequency because everything the monitoring step needs either arrives under this clause or does not arrive. Budget the staff time to check compliance and attach a consequence to failing it, as a condition nobody verifies is a condition nobody meets. And provide for the operator disappearing, since in a thin market the replacement you would turn to may not exist.
Running the delivery
Test small before you build permanent
The Utrecht lab tested a modular solar-powered charging station, with vocational and applied-sciences students and its operator partners. The station would charge shared cargo bikes where they are parked, saving operators the trips needed to collect and relocate them. The work reached a first physical prototype, but the station had still not been placed in public space at the time of writing because a suitable site and the necessary permissions were held up. The operators it was designed with also changed along the way.
The Vienna lab went the other way entirely. Instead of building, it reactivated an underused space in Liesing as a flexible activity hub, with cultural and food offers, and invited residents and local initiatives to help shape and run it, recruiting the people behind the offers through a neighbourhood platform they already used. Next to it stood a temporary bike-sharing station that needed no docking infrastructure at all, since it worked as a designated area inside the city's existing mobility app. The whole thing was set up and operating across roughly six weeks of one summer (Deliverable 6.1).
Neither route is the better one. They suit different stages in the life of a measure. The question to settle before delivery starts is which measures in your package you are confident enough to build outright, and which ones should be tried in a reversible form first while the capital is still uncommitted.
Produces evidence, and a working relationship with the people who might use the permanent version, inside a single season and for very little money. The DREAMS review makes the same point about hubs generally, that a tactical approach lets them be prototyped and tested before anything is made permanent (Deliverable 2.2).
Commits capital and leaves a permanent asset that is difficult to reverse. The right call once a measure has already proved itself.
Record it while it happens
Alongside measuring what an intervention achieved, DREAMS evaluates how it was implemented, looking at the decisions taken, the governance and stakeholder dynamics around them, the logistical and organisational problems that came up, and whether administrative delay played a part (Deliverable 6.1). That work is mostly interviews and conversation, and it is much easier while people still remember.
Keep a short-dated record of each deviation and the decision taken in response, from the first day of delivery. It costs very little, and it is what makes the next two steps possible. An indicator that comes back disappointing has two quite different explanations, that the measure was the wrong one or that it was never delivered as designed, and only the delivery record separates them. The same record is what lets the final step pass on something another outskirt can actually use, which is rarely the measure itself and almost always the account of what it took to get it built.