← Work & Learning

PROJECT NOTEBOOK / CITIES AS SYSTEMS

From a walk to the systems of a city.

How do we evaluate a greenway, rebalance shared bikes or introduce a district online? Three Cornell course projects approach the experience of a city from different directions.

A retrospective of team coursework, read alongside the original material and the individual contributions recorded in the project fieldbook.

About 12 min read
100%

SYSEN 5400 / 17 MAY 2023

Greenways: inspect the measure before the ranking.

The Pedestrian Greenway Optimization System report begins with stakeholders, translating resident, visitor, business and public-service perspectives into goals, decisions, metrics and utility functions. Candidate choices include space types, paths and vegetation.

The team describes generating and checking 10,000 candidate architectures, then using Pareto and fuzzy-Pareto analysis to identify options worth considering. Cost, satisfaction and visitor-related measures shape that comparison.

The report also leaves useful questions open. When cost and performance behaved unexpectedly, it revisited the performance measure. Its conclusion identifies the influence of simulated survey data and the need for on-the-ground observations. I would read those checks alongside the candidate results.

On revisiting the research, I would ask whether another design improves one of cost or performance without worsening the other. If not, the candidate merits further comparison. Whose experience does the performance measure represent, and would different simulated inputs move it off the frontier? Pareto analysis narrows the options; the final choice still needs a concrete account of the needs.

  1. 01

    Needs to goals

    Identify the participants and connect their needs to design goals.

  2. 02

    Generate and filter

    The report describes 10,000 candidate architectures, checked for duplicates and constraints before evaluation.

  3. 03

    Compare and review

    Use Pareto analysis to find candidates, then examine how the evaluation measures shape the results.

Source locations: §§2, 3.2.3, 3.5 and Conclusion. My contribution & reflection ↗

CHEME / SYSEN 6800 · 21 NOVEMBER 2022

Shared bikes: keep rentals and returns together.

The Citi Bike coursework examines a docked network where one station can run out of bikes while another runs out of space. Its model considers relocation costs together with penalties for unmet rental and return demand, using assumed station supply and demand.

The original records an incomplete implementation: the penalty terms were not correctly connected and the model returned zero relocations. This is a reason to inspect the implementation too: does the objective actually include the problem we want to address, and do the constraints express the intended design?

The experiment below reduces the question to three stations. Rebalance by hand, inspect each demand phase, then price all three outcomes: how much unmet service does one more move avoid?

Zero relocation can have very different explanations. An omitted penalty hides service loss from the objective. With all three costs included, expensive relocation may still make no movement optimal. Read the service gaps and cost breakdown alongside the minimum value. Below, change the penalties, inspect price boundaries and load an allocation back into the stations to check it.

Course number follows the original cover. Source locations: Model Introduction, Model Implementation and Conclusion. Read the project entry ↗

REBALANCE IT / AN INDEPENDENT 2026 DEMONSTRATION

A bike to borrow. A dock to return to.

Three fictional stations, eight docks each and twelve bikes initially. Rebalance first, then serve rentals followed by returns. Try to reduce unmet demand while keeping the number of moves in view.

B needs bikes, while A needs room for incoming returns.

Station A

7/ 8

1 empty docks

Rental demand
1
Return demand
4

Station B

1/ 8

7 empty docks

Rental demand
6
Return demand
0

Station C

4/ 8

4 empty docks

Rental demand
2
Return demand
2

Rebalancing preserves the total number of bikes. Each transfer counts as one bike moved.

Unmet rentals55 without rebalancing
Unmet returns22 without rebalancing
Planned moves0bikesTransfers in either direction are counted
Model assumptions and station-by-station results

Any two stations can exchange bikes directly; distance, travel time and equipment are omitted. Demand is known in advance. Rentals precede returns, ride durations are not tracked, and incoming bikes can come from outside the network. All situations and values are authored for this site demonstration.

Current plan / one rental-and-return cycle
StationRebalancedAfter rentalsAfter returnsRental gapReturn gap
A76802
B10050
C42400

OBJECTIVE AUDIT / THE SAME STATIONS, A DIFFERENT TRADE-OFF

Is a move worth it? Count the cost of leaving demand unmet.

Start with relocation cost alone, then restore the penalties for unmet rentals and returns. Every allocation is enumerated to find the lowest combined cost. All prices are fictional cost units for this exercise.

Each value: 0–100 units. Apply after editing; use the same unit for all three costs.

RELOCATION ONLY

No moves. Zero counted cost.

5 rentals and 2 returns remain unmet.

At these penalties, the omitted service cost is 28 units.

COMBINED OBJECTIVE

Minimum total cost 5

Moves 5 + rentals 0 + returns 0 = 5 units.

A/B/C: 2 / 6 / 4; minimum 5 moves. 3 allocations share the minimum.

YOUR CURRENT PLAN ABOVE

Current total cost 28

Moves 0 + service penalties 28 units; 23 above the minimum.

Charged for all 0 planned moves, including backtracking.

A displayed tie is resolved by fewer moves, fewer total unmet requests, then smaller A/B allocations. A zero penalty removes that service measure from the cost objective; it does not satisfy the demand.

Open the frontier: what do extra moves buy?

Keep allocations with a trade-off between relocation count and service penalties. Multiple allocations can share a point; a heavier ring marks a minimum-cost point at the current relocation price.

Pareto frontier of moves and service penaltiesHorizontal: minimum bikes moved. Vertical: weighted rental and return penalties. The table below gives every point and a loadable allocation.Service penalties (units)Minimum bikes moved028120212384450
The line connects feasible allocations. Intermediate points need not be feasible: station bike counts are whole numbers.
One representative allocation at each frontier point
Min. movesService penaltyAllocations at pointA / B / CAction
02817 / 1 / 4
12016 / 2 / 4
21215 / 3 / 4
3824 / 4 / 4
4433 / 5 / 4
5032 / 6 / 4
Open sensitivity: when does the relocation price change the recommendation?

Hold rental and return penalties at 4 and 4; vary the relocation price continuously from 0 to 20 units. The table shows one optimum in each open interval. Fractions denote exact boundaries.

Optimal allocations inside intervals; endpoints listed separately
Move price (open interval)A / B / CMin. movesUnmet rent / returnTies
0 < c < 42 / 6 / 450 / 03
4 < c < 85 / 3 / 423 / 01
8 < c < 207 / 1 / 405 / 21
  • Price = 0: 9 optimal allocations, with move counts 5 / 6 / 7.
  • Price = 4: 9 optimal allocations, with move counts 2 / 3 / 4 / 5.
  • Price = 8: 3 optimal allocations, with move counts 0 / 1 / 2.
  • Price = 20: 1 optimal allocations, with move counts 0.
Audit all 61 allocations and costs

Every allocation is charged its minimum relocation count; distance and travel time are omitted. Total bikes stay at 12, each station holds 0–8, and rentals precede returns.

Applied prices: move 1, rental 4, return 4
A/B/CMovesUnmet rentalsUnmet returnsMove costService penaltyTotalOptimal
2/6/4500505Yes
3/6/3500505Yes
4/6/2500505Yes
1/6/5600606—
1/7/4600606—
2/7/3600606—
3/7/2600606—
1/8/3700707—
2/8/2700707—
3/5/4410448—
4/5/3410448—
5/5/2410448—
2/5/5510549—
5/6/1510549—
1/5/66106410—
4/7/16106410—
0/6/67107411—
0/7/57107411—
0/8/47107411—
3/8/17107411—
4/4/43203811—
5/4/33203811—
3/4/54204812—
2/4/65205813—
1/4/76206814—
5/7/06206814—
0/5/77207815—
4/8/07207815—
5/3/423021214—
4/3/533031215—
6/4/232131215—
3/3/643041216—
6/5/142141216—
2/3/753051217—
6/6/052151217—
1/3/863061218—
0/4/873071219—
5/2/524021618—
6/3/323121618—
4/2/634031619—
3/2/744041620—
2/2/854051621—
6/2/414112021—
5/1/625022022—
7/3/223222022—
4/1/735032023—
7/4/133232023—
3/1/845042024—
7/5/043242024—
6/1/515112425—
7/2/314212425—
5/0/736032427—
4/0/846042428—
7/1/405202828—
6/0/626122830—
8/2/224322830—
8/3/134332831—
8/4/044342832—
7/0/516213233—
8/1/315313233—
8/0/416313637—

The original report’s model, implementation and conclusion document the gap between intent and implementation. These three newly authored stations illustrate an omitted service penalty. The earlier reference plan above still minimises unmet requests first, then moves; compare the two objectives.

Return to the original implementation retrospective ↑

CHERRY STREET / DESIGN CONCEPT

A district online: what is here, and where next?

The Cherry Street presentation proposes a Business Improvement District as a future possibility. Its website and social-media concept helps visitors understand the place through area information, business and location maps, imagery, contact information and directions.

It considers starting with an existing visitor-information platform, then building an independent presence as the area develops. Social media, logos and other branding material are meant to connect to that presence. The material documents a proposal.

Building my own site brings me back to those practical questions: where does someone arrive, what do they want to understand, and where can they go next? Organising those routes deserves the same care as the visual design.

If I developed the proposal further, I would review one visitor journey: after finding a business, can someone confirm its location, get directions and return to exploring the district? Then I would switch to upkeep: who updates a changed listing, and do the map and social channels change with it? These are checks I would add in a present-day review.

Meet the placeFind useful informationPlan a visit

Source locations: Website Focus, Future Website Development and Connections with Other Branding Methods. Read the project entry ↗

ORIGINAL MATERIAL & FURTHER READING

Keep the work and its context together.

  • Pedestrian Greenway Optimization SystemSYSEN 5400 · 17 May 2023 · team report
  • NYC CITI Bike Parking, Bike Availability Optimization and Profit MaximizationCHEME/SYSEN 6800 · 21 November 2022 · team report
  • Cherry Street BID Intro, Web/Social Media Branding and InteractionCourse presentation · district and digital-branding proposal

This notebook was checked against the original coursework listed above. Individual contributions and later reflections can be read in the project fieldbook.

AFTER READING / THE CONVERSATION

What would you add?

Account & reading space ↗

Add an experience, ask a question or point out a correction. Both language editions share this article’s discussion.

Public comments are not open yet. Keep a draft on this device, or send your thoughts through the contact page.

Write a local draft

Only “Save on this device” stores the draft. Clear it on shared devices; it is not published automatically.

0 / 1600

Send it through the contact page ↗

Same moment / Different meridians

A moment, shared.

Your time, alongside mine.

Your time

— : —

Waiting for the browser clock

—

Ronaldo’s time

— : —

Waiting for the browser clock

Asia/Singapore

Enable JavaScript to see local time and the time difference.

The weather where you are

Enable JavaScript for city and weather.

IP location may point to a network exit. Device location can refine it.

Your clock uses your browser; mine is set to Singapore. IP city and weather are cached in this browser session for 30 minutes. Device location needs permission; rounded coordinates are used for weather and aren’t saved by this site.

IP · ipwhois.io ↗Weather · Open-Meteo ↗