<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Benjamin de la Pena on Medium]]></title>
        <description><![CDATA[Stories by Benjamin de la Pena on Medium]]></description>
        <link>https://medium.com/@benjiedlp?source=rss-f48e59011a1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*lCkRUaLMenxGAccq4IP2sg.jpeg</url>
            <title>Stories by Benjamin de la Pena on Medium</title>
            <link>https://medium.com/@benjiedlp?source=rss-f48e59011a1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 10:21:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@benjiedlp/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Prescription: Buy out the jeepneys, solve social distancing, and reform the transportation system]]></title>
            <link>https://medium.com/@benjiedlp/prescription-buy-out-the-jeepneys-solve-social-distancing-and-reform-the-transportation-system-7e0b45eea3a7?source=rss-f48e59011a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e0b45eea3a7</guid>
            <category><![CDATA[covid-19-crisis]]></category>
            <category><![CDATA[transportation]]></category>
            <category><![CDATA[informal-economy]]></category>
            <category><![CDATA[metro-manila]]></category>
            <dc:creator><![CDATA[Benjamin de la Pena]]></dc:creator>
            <pubDate>Thu, 30 Apr 2020 21:05:25 GMT</pubDate>
            <atom:updated>2020-05-01T16:33:34.490Z</atom:updated>
            <content:encoded><![CDATA[<h4>A proposal to use the pandemic stimulus to reform informal transportation</h4><blockquote>“A crisis is a terrible thing to waste.” Nobel Laureate Paul Romer</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TJVhk9Z6cQ7KMy2lORVyzQ.jpeg" /><figcaption>photo by Stephanie Azarias &amp; Alexander Olpindo (Wikipedia Takes Manila participant) CC Share-alike 3.0</figcaption></figure><p>Metro Manila runs on privately provided public transportation. The jeepneys and buses receive no government money but earn all their income from their fares. This is par for the course for most cities in the global south.</p><p>The coronavirus lock down and the full ban on public transportation in Metro Manila means that all of the drivers, owners, and operators of these vehicles have no income.</p><p>Up to 80% of the commuters in Metro Manila travel by public transport. This includes essential workers and medical and emergency personnel. Anything we can do to improve public transportation improves the city for the vast majority of its residents and workers.</p><h3>What if I told you that we could save the livelihoods of jeepney operators and drivers, provide efficient and free public transportation, enforce social distancing, change driver behavior, AND reform the transportation sector?</h3><p>The key is to use the economic rescue package to pay operators and drivers to run their routes.</p><p>Here’s how we do it:</p><h4>1. Government should PAY jeepney drivers to run their routes</h4><p>This would be part of the economic rescue package.</p><p>Government pays the equivalent daily income of the bus or jeep. This would not be too expensive relative to the costs of the lock down and the total economic rescue.</p><p>Jeepneys account for 40% of all our trips in the mega city. There are 55,000 franchised jeepneys and 5,000 buses in Metro Manila. (<a href="https://www.changing-transport.org/modernizing-public-transport-in-the-philippines/">Mariano, Patricia. “Modernizing Public Transport in the Philippines” in Changing Transport</a>.)</p><p>A jeepney brings in about PhP 4,000 a day, of which the driver takes home PhP 700. The rest goes to the <em>boundary</em> (vehicle rent — which is the operator’s revenue), fuel, and maintenance.</p><p>There are about 55,000 jeeps in Metro Manila. The total daily cost of buying jeepney service would be Php 172M. That’s just .05% of the total coronavirus economic stimulus package for the Philippines (PhP 330B).</p><p>If we ran the program for 90 days, it would cost PhP 15.5B, or less than 5% of the total stimulus. I think that is well worth the cost of keeping Metro Manila running.</p><p>(I do not have income numbers for buses but I’m sure it would be a fraction of the total cost of buying jeepney service.)</p><p>Buying the daily routes gives the government leverage to do the following:</p><h4>2. Make public transportation free</h4><p>The jeepneys don’t have to charge fares because the government is paying them to run the routes.</p><p>The free fares is money back into the pockets of commuters.</p><h4>3. Effect social distancing rules in public transport by reducing the number of riders</h4><p>The government can then effectively prescribe limits to ridership, e.g. only 10 people allowed on a jeepney that can carry 18.</p><p>The drivers will comply because it doesn’t affect their income.</p><h4>4. Change driver (and system) behavior</h4><p>Because we break the passenger = driver income link, drivers will not be swerving in and out of traffic to pickup passengers (and earn fares).</p><p>The government can impose performance standards that could include:</p><ul><li><strong>organized stops </strong>—we can designate jeepney stops along the routes and require drop offs and pick-ups only in the stops.</li><li><strong>required trip completion times</strong> —we can impose an average time to complete a one-way route (depending on the route) and require the drivers to comply.</li><li><strong>safe driving standards</strong> — by suspending or barring any driver caught violating road rules. (We can even impose speed limits based trip completion times)</li><li><strong>Set headways and controlled dispatching</strong>— we can control the time between jeepneys by defining and imposing head ways at the start of the routes (e.g., depending on demand: 1 jeepney every 3 minutes at peak, 1 jeepney every 5 or 7 minutes off-peak). We can set up dispatches at the either end of the route, they will need it to verify route completion anyway</li><li><strong>Use GPS based-tracking and verification </strong>— drivers will be required to check in at the start and end of every route to confirm that they ran the route. It will be easy enough to put together a proximity based phone app and require drivers to upload an app that traces their routes and “clocks” them into the route. Dispatchers with compatible apps can check them in and check them out of the route.</li><li><strong>Get passenger counts </strong>—we can require drivers to complete simple forms at the end of each route to give a close estimate of the number of riders they carried. Later on, this system can be digitized and automated so we get more accurate (and daily) origin and destination data.</li></ul><p>Setting up the system above sets the stage for better management of our public transportation system and, in the post-COVID-19 world, allows us to:</p><h4>5. Fully reform public transportation</h4><p>This pilot will show us that reforming the economics of privately provided public transportation will change the behavior of the system.</p><p>We would have changed the incentives that drive the system.</p><p>Drivers will drive safer. Trips will be much more predictable. Commuters will save time and money.</p><p>We would have changed the way we think about what is possible and open us to new ways of funding transportation. Buying jeepney trips for a whole year, paying the drivers and operators out of government funds, will cost about PhP 65B. That is just 1/100th of the total GDP of Metro Manila (PhP 6 Trillion) and just about 12 days of the <a href="https://cnnphilippines.com/news/2018/09/19/JICA-study-traffic-5-billion.html">supposed economic cost of traffic congestion</a>.</p><p>Later on, we can add: more stringent performance standards (including emissions controls) fixed salaries and labor standards; cashless fare collection; electric vehicles.</p><p>This is a crisis. This is also an opportunity.</p><p>We should seize it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e0b45eea3a7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Concluding Notes — Transportation Information Infrastructure Plan]]></title>
            <link>https://medium.com/@benjiedlp/concluding-notes-transportation-information-infrastructure-plan-14a7cb2c4bd5?source=rss-f48e59011a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/14a7cb2c4bd5</guid>
            <category><![CDATA[cities]]></category>
            <category><![CDATA[infrastructure]]></category>
            <category><![CDATA[transportation]]></category>
            <category><![CDATA[information]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Benjamin de la Pena]]></dc:creator>
            <pubDate>Wed, 08 Jan 2020 14:57:00 GMT</pubDate>
            <atom:updated>2020-01-08T14:57:00.671Z</atom:updated>
            <content:encoded><![CDATA[<h3>Concluding Notes — Transportation Information Infrastructure Plan</h3><h4>This is part 20 and the final part of a serialized, draft, generic transportation information infrastructure plan meant to help municipal departments of transportation to manage the emerging urban transportation ecosystem</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iLElrtIDTOYY61vWXjpchg.png" /><figcaption>(Graphic by <a href="http://www.xiolugo.com/">Xio Lugo</a> of <a href="https://story2designs.com/">Story2 Designs</a>.)</figcaption></figure><p>Transportation has always been driven by and enabled by technology. From sandals to the wheel; from the stirrup to the internal combustion engine; from the turnpike and pavement to the synchronized traffic light — technology helps people get to where they want to go.</p><p>Each improvement in technology has helped people to move more and move faster. But each new technology has also created demands for more technology and more management:</p><ul><li><em>Wheeled wagons worked better with cleared paths which led to the technology of road-building.</em></li><li><em>Building and maintaining roads, even in the age of wagons, required money so localities invented “turn pikes” that exacted tolls from wagons traversing paved roads.</em></li><li><em>Tar and cobblestone streets and roads became part of city infrastructure.</em></li><li><em>Cities invented one-way roads to keep traffic moving, and then invented sidewalks to give people space to walk — away from horse manure on the streets.</em></li><li><em>Horse-drawn buses gave way to motor buses.</em></li><li><em>Trains went underground to become subways.</em></li><li><em>Along the way, new rules and new standards were developed to make sure people could get to where they want to go.</em></li></ul><p>Each new technology made the system more complex and required a change in the institutions that managed it. Departments of street sweepings became departments of roads and public works, and then became departments of transportation.</p><p>The rapid change ushered in by information technology-enabled transportation also requires a change in institutions. For a municipal department of transportation, this plan is the road map to that change. While the institutional capacities may need to change, the remit does not: The goal is to ensure that whenever anyone makes a trip in the city, they are equipped with relevant information to make that trip easier, less costly, healthier, and more sustainable.</p><p>This effort though sets up other challenges, questions that a DOT needs to answer:</p><ul><li><strong><em>How will the city fund its transportation information investments?</em></strong></li><li><strong><em>How will the department develop the resources to train staff and acquire the institutional skills it needs to function in this new space?</em></strong></li></ul><p>As the primary infrastructure manager, a city DOT needs to manage not just the physical (and jurisdictional) right of way, but also the information that flows into and out of it.</p><p>This is draft, generic plan is a guiding document for a department to prepare for and thrive through an uncertain future where generational transition, disruption, shifting economics, and oncoming environmental pressures will change forever the way people move through the city. We hope the plan keeps the department technologically resilient, and ultimately makes the city a better place to live both now and in the future.</p><p><strong><em>*end*</em></strong></p><p><em>I drafted this plan with </em><a href="https://medium.com/u/93bd012e5141?source=post_page-----fcf6f27aa185----------------------"><em>Alex Hagenah</em></a><em>, </em><a href="https://medium.com/u/fa908e9a07d1?source=post_page-----fcf6f27aa185----------------------"><em>Sam Marshall</em></a><em>, and </em><a href="https://medium.com/u/9021d9e983b6?source=post_page-----fcf6f27aa185----------------------"><em>Mary Alyce</em></a><em> Eugene, my team mates and former colleagues when I served as the Seattle Department of Transportation’s Chief of Strategy and Innovation. (Our work was shaped by the very helpful insights and inputs from 30+ of our SDOT colleagues.)</em></p><p><em>I have the department’s permission to share the draft plan with whoever asks. Connect with me on </em><a href="https://www.linkedin.com/in/bdelapena"><em>Linked.In</em></a><em> and send me a DM and I will send you a link to the pdf and .docx copies.</em></p><p><em>Feel free to crib, copy, and steal the materials for your city.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14a7cb2c4bd5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Future needs and skill sets for city DOTs]]></title>
            <link>https://medium.com/@benjiedlp/future-needs-and-skill-sets-for-city-dots-e14d78835181?source=rss-f48e59011a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/e14d78835181</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[transportation]]></category>
            <category><![CDATA[infrastructure]]></category>
            <category><![CDATA[information]]></category>
            <category><![CDATA[cities]]></category>
            <dc:creator><![CDATA[Benjamin de la Pena]]></dc:creator>
            <pubDate>Tue, 07 Jan 2020 14:49:51 GMT</pubDate>
            <atom:updated>2020-01-07T14:52:50.145Z</atom:updated>
            <content:encoded><![CDATA[<h4>This is part 20 of a serialized, draft, generic transportation information infrastructure plan meant to help municipal departments of transportation to manage the emerging urban transportation ecosystem</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0-2p08yom6CMvoGu9tI_oQ.png" /><figcaption>(Graphic by <a href="http://www.xiolugo.com/">Xio Lugo</a> of <a href="https://story2designs.com/">Story2 Designs</a>.)</figcaption></figure><p>To implement the policies, projects, initiatives, and technology investments outlined in this draft, generic plan, municipal DOTs have to develop new skills and capacities. These skills are necessary if the DOT is to manage an urban transportation system built on information and to engage the actors in the emerging ecosystem.</p><p>This draft, generic plan recommends the following actions:</p><h4>Build data awareness across the enterprise</h4><p>All DOT staff should appreciate how the department collects and stores information and data, and how the department uses the data.</p><p>A department’s on-boarding process for all new hires should include introductory training sessions on the DOT’s datasets (preferably through a DOT Data Library). It should also schedule briefings and training sessions for existing employees so that all DOT staff know what data is available and how to get it.</p><h4>Clarify roles between the DOT and city IT Department</h4><p>If the city has a centralized IT department that owns the remit for information technology expertise across city government, the DOT should a develop a close working relationship with the IT department. The DOT should make sure it keeps (or gains back) the authority to make strategic technology decisions and manage mid-level system enhancements and IT projects.</p><p>DOTs need to exercise authority over business intelligence requirements. The department’s executive leadership should involve itself with IT decisions at the strategic level. <strong><em>Information technology systems purchases should be treated as strategic investments and should satisfy enterprise-wide requirements.</em></strong></p><p>The DOT and the city IT department particularly need to clarify roles and process for deploying and operating cloud-based solutions. The demands of the emerging transportation information ecosystem requires the speed and bandwidth of cloud services. The process between the two agencies must be equal to the demands for agility and speed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/288/1*_EkVcCTH8ClrNAeV7DRqRg.png" /><figcaption>(Graphic by <a href="http://www.xiolugo.com/">Xio Lugo</a> of <a href="https://story2designs.com/">Story2 Designs</a>.)</figcaption></figure><h4>Educate staff on new map technology and systems</h4><p>Usually, a large contingent of DOT staff are trained and are fluent with ESRI’s ArcGIS. A smaller number understand the spatial databases behind GIS and how they interact with map visualizations. Often, only a handful understand web map services or how to deliver data to web map services.</p><p>The actors of the ecosystem (information and mobility service providers) build their enterprises on web map services from the ground up. Their workforce code in the computer programming language on which these services were built (Python, GeoJSON, C#, R, etc.). While DOT staff may not need to program or code, they should be familiar with the structure of these languages and how they work.</p><p>These skills are necessary (particularly for an Information Data Unit) as the DOT builds up its API strategy and rolls out data feeds and APIs.</p><h4>Hire and/or train for skills in problem-solving, basic programming, and data analytics</h4><p>The demands of the new ecosystem require more capacity in data analytics and problem-solving. Particular classes of DOT staff should be hired with these skills along with rudimentary or basic programming skills.</p><p>A city DOT’s use of data analytics will only continue to grow as more technology takes over the transportation system. Data analytics work that DOTs currently outsource may need to be brought in-house may need to be brought in-house so that the department continues to acquire institutional expertise in the data it collects.</p><p>For analyst and program positions, using spreadsheets and manipulating and querying databases should be basic skills.</p><p>City DOTs should train more staff in data visualization (such as Tableau and/or Power BI).</p><p>DOT staff should also be fully versed in open-source platforms such as GitHub or its alternatives, where a lot of open code is developed and tested.</p><h4>Benchmark skills against the industry</h4><p>DOTs should commission a review of the skills required by the information and mobility service providers against their department’s own workforce skills profile. This will ensure that DOT teams understand their counterparts from the information and transportation providers.</p><h4>Invest in in-house knowledge in machine learning and AI</h4><p>The next innovations in transportation technology are being built on machine learning and AI. DOTs need to be conversant in these technologies to manage the implications of these on transportation.</p><h4>Learn Lean and Agile methodologies</h4><p>The emerging ecosystem requires faster responses from DOTs and the ability to deliver new information products quickly.</p><p>Lean and Agile both focus on the needs of the customer. Lean builds a culture of continuous improvement and the elimination of process steps that do not bring value to the customer. Agile builds a culture of responsiveness and collaboration for rapid delivery of what the customer needs.</p><h4>Build In-house UX/UI Testing Capacity</h4><p>To better serve the information needs of users of our transportation system, a DOT needs to build a culture of user testing. User tests of proposed new processes or technologies can reveal inadequacies <em>before</em> they become issues. They can also save the department from locking itself into a solution that doesn’t fully meet the needs of users. In the long-run, this saves time and money for the department, and improves user experiences.</p><p>Currently, user testing is often not conducted before committing to a new process or technology, and when it is, the work is usually contracted out to expensive consultants. DOTs need to build in-house expertise in this area so that testing can be streamlined and cost-effective.</p><h4>Gain skills in product management and development</h4><p>The initiatives listed in this plan require not just <em>project</em> management but also <em>product </em>management.</p><p>Here’s <a href="https://blog.aha.io/the-product-manager-vs-project-manager/">the difference in the roles</a>:</p><blockquote><strong>“Product manager</strong>(s)<em> — </em>…set the strategy, prioritize releases, talk to customers, and clearly define features. Their efforts are ongoing and involve managing the entire lifecycle of the product. A product manager’s goal is to deliver a product that customers love.</blockquote><blockquote><strong>“Project manager</strong>(s)<em> — </em>oversee a fixed project from beginning to end. It can be a single project or a group of projects. Their job is to execute the strategy set by the product manager or leadership team. A project manager’s goal is to work with a broader team with a diverse set of skills and to complete a project on time and under budget.”¹</blockquote><p>Most DOTs have a deep bench in project management but little or no capacity at all in product management, particularly for information products. Product management also demands customer- or user-driven approaches.</p><h4>Build communities of practice within the DOT</h4><p>A municipal DOT needs to keep up with innovations in how data is managed, handled and analyzed. The department should be intentional in sharing new knowledge and skills across its workforce.</p><p>Communities of practice will build the informal social networks and social capital a DOT needs to leverage the information it collects and to adapt to the rapidly changing ecosystem.</p><p><em>Up next: </em><a href="https://medium.com/p/e14d78835181/edit?source=your_stories_page---------------------------"><strong><em>A</em></strong></a><strong><em> concluding note</em></strong></p><p><em>I drafted this plan with </em><a href="https://medium.com/u/93bd012e5141?source=post_page-----fcf6f27aa185----------------------"><em>Alex Hagenah</em></a><em>, </em><a href="https://medium.com/u/fa908e9a07d1?source=post_page-----fcf6f27aa185----------------------"><em>Sam Marshall</em></a><em>, and </em><a href="https://medium.com/u/9021d9e983b6?source=post_page-----fcf6f27aa185----------------------"><em>Mary Alyce</em></a><em> Eugene, my team mates and former colleagues when I served as the Seattle Department of Transportation’s Chief of Strategy and Innovation. (Our work was shaped by the very helpful insights and inputs from 30+ of our SDOT colleagues.)</em></p><p><em>I have the department’s permission to share the draft plan with whoever asks. Connect with me on </em><a href="https://www.linkedin.com/in/bdelapena"><em>Linked.In</em></a><em> and send me a DM and I will send you a link to the pdf and .docx copies.</em></p><p><em>Feel free to crib, copy, and steal the materials for your city.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e14d78835181" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ecosystem policy directions and further considerations]]></title>
            <link>https://medium.com/@benjiedlp/ecosystem-policy-directions-and-further-considerations-1546e08a09ab?source=rss-f48e59011a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/1546e08a09ab</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[cities]]></category>
            <category><![CDATA[transportation]]></category>
            <category><![CDATA[infrastructure]]></category>
            <category><![CDATA[information]]></category>
            <dc:creator><![CDATA[Benjamin de la Pena]]></dc:creator>
            <pubDate>Fri, 03 Jan 2020 20:31:10 GMT</pubDate>
            <atom:updated>2020-01-03T20:31:10.889Z</atom:updated>
            <content:encoded><![CDATA[<h4>This is part 19 of a serialized, draft, generic transportation information infrastructure plan meant to help municipal departments of transportation to manage the emerging urban transportation ecosystem</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5YivKeeQEXSpujKt8n8PiQ.png" /></figure><p>For DOTs that subscribe to <a href="https://nacto.org/2019/05/30/managing-mobility-data/">NACTO’s policy guidance on managing mobility data</a> (2019, co-prepared with the International Municipal Lawyers Association), the document provides best practices for access to and management of mobility data and “a common framework for sharing, protecting, and managing data based on four principles:</p><blockquote><strong>Data is a Public Good</strong>: Cities require data from private vendors operating on city streets to ensure positive safety, equity, and mobility outcomes on streets and places in the public right-of-way.</blockquote><blockquote><strong>Data Should be Protected</strong>: Cities and private companies should treat geospatial mobility data as they treat personally identifiable information (PII).</blockquote><blockquote><strong>Data Should be Collected Purposefully</strong>: Cities should be clear about when, why, and what data is necessary for planning, analysis, oversight, and enforcement purposes.</blockquote><blockquote><strong>Data Should be Portable</strong>: Open data standards help cities and private companies to share data in universal formats, enabling cities to use data from multiple sources, and supporting innovation in both the public and private sectors.”</blockquote><p>To protect the privacy of individuals and safeguard the community, <strong><em>DOTs should explore the following policy directions</em></strong> to apply to the actors in the ecosystem:</p><h3><strong><em>Transportation information fiduciaries</em></strong></h3><p>The ability of information and mobility service providers to gather vast amounts of location information about their users while controlling what information they deliver to the user is a significant power asymmetry. The location information is unique to each individual, representing how that individual moves across the city. While a single instance of geolocated data attributed to a user may be neutral, geolocated data across a geography and across time is categorically personally identifiable information.</p><p>DOTs should explore policies that designate transportation information service providers and mobility service providers as “information fiduciaries” who must maintain an explicit relationship of trust with their users and with the other actors in the system.</p><p>The <a href="https://www.eff.org/deeplinks/2018/10/information-fiduciaries-must-protect-your-data-privacy">Electronic Frontier Foundation explains the idea</a>:</p><blockquote>“The law of ’fiduciaries‘ is hundreds of years old. It arises from economic relationships based on asymmetrical power, such as when ordinary people entrust their personal information to skilled professionals (doctors, lawyers, and accountants particularly). In exchange for this trust, such professionals owe their customers a duty of loyalty, meaning they cannot use their customers’ information against their customers’ interests. They also owe a duty of care, meaning they must act competently and diligently to avoid harm to their customers. These duties are enforced by government licensing boards, and by customer lawsuits against fiduciaries who do wrong.”</blockquote><p>Among the implications of exploring this policy framework, DOTs should consider the following:</p><ul><li>All information and mobility service providers may be required to register with the city and the DOT and be assigned a unique provider identifier that will be used as metadata for APIs and data feeds.</li><li>The unique ID may also be used to validate data agreements with other actors in the ecosystem and help track data breaches.</li></ul><h3><strong><em>Policies for providers</em></strong></h3><p>To meet the information infrastructure and ecosystem goals, service providers must have:</p><ul><li>Written and published company commitments against racism and discrimination</li><li>Express privacy rules and anti-surveillance commitments</li><li>Explainable algorithms for machine learning and AI systems</li><li>A framework for delivering information to users on the impact of their services on the environment (specifically their contribution to factors driving climate change)</li><li>Commitments and protocols to notify their users and the rest of the ecosystem immediately of critical data breaches</li><li>Disclosure on how they use data provided and generated by their users</li><li>Declared strategies for delivering information via non-digital means, and means appropriate for the disabled</li><li>Non-digital and non-credit card payment options</li><li>Agreed-upon information accuracy/dependability goals (across all actors)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/230/1*nXhg0xQPwfS__kyvNNk_wA.png" /></figure><p><strong><em>APIs and data feeds</em></strong></p><p>To ensure that the transportation network can serve and meet the information needs of the traveling public effectively, <strong><em>DOTs should encourage the providers to work with the DOT to develop APIs that will allow the provider to ingest data from the DOT and vice versa</em></strong>.</p><p>The data from the DOT may include, but is not limited to:</p><ol><li>Real-time road closures (scheduled and un-scheduled)</li><li>Real-time prioritized or recommended routes or re-routes</li><li>Curb management information (loading, parking, and ride-hailing zones)</li><li>Real-time parking and load zone availability</li><li>Geo-fenced areas (where pickups or drop-offs may not be allowed, or particular vehicles may be restricted)</li><li>Fees and rate schedules</li><li>Route advisories</li><li>Emergency advisories</li></ol><p><strong>Providers should push out information (in feeds and APIs) on the following:</strong></p><ol><li>Estimated carbon generated per user and per trip</li><li>Aggregate carbon generated by all users and all trips they provide</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/445/1*7Bovu4cgCk_ZS0gUJ1in3w.png" /></figure><p><strong><em>For high-capacity mobility providers. </em></strong><em>(trains, buses, shuttles, vanpools)</em></p><ol><li>Routes and schedules</li><li>Re-routes and changes in schedule (particularly re-routes during emergencies)</li><li>Real-time vehicle locations while in service</li><li>Real-time passenger counts</li><li>Wait times/time to next vehicle</li><li>Historic reliability of each route (% of time on time or delayed)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/235/1*x8UY_jvDhfhYc7v8zV59EQ.png" /></figure><p><strong><em>For shared service providers </em></strong><em>(car-share, ride-hail, micro-mobility)</em></p><ol><li>Aggregated origin and destination data</li><li>Aggregated, real-time vehicle flow data while in arterials, urban centers and urban villages (volume of vehicles, average speeds)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/333/1*5xMGJOeHoO8aZcQWXaMPaQ.png" /></figure><p><strong><em>For car-share and micro-mobility providers</em></strong></p><ol><li>Current locations and service status (usable, disabled) of available vehicles</li><li>Current rates/fares and historical average</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/274/1*V3xt2EVUIPJjHs5OiA5R5Q.png" /></figure><p><strong><em>For urban goods delivery services</em></strong></p><ol><li>Aggregated, real-time vehicle flow data while in arterials, urban centers and urban villages</li><li>Aggregated predicted delivery vehicle volumes</li><li>Aggregated historical data on delivery vehicle volumes</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/179/1*_A-yeKTmCTjQSxVfj3SVmw.png" /></figure><p><strong><em>For map and navigation service providers</em></strong></p><ol><li>Aggregated (also anonymized and obscured) data on historical vehicle and traveler flows and volumes</li><li>Predicted vehicle and traveler flows</li><li>Real-time notification on unusual spikes in traffic volumes</li><li>Receive information from and transmit information to other providers on:</li></ol><ul><li>All available transportation options</li><li>Nearest available transportation (distance, time, accessibility)</li></ul><h4><strong>Safety and security</strong></h4><p>All providers should make it easy to call for help through their vehicles, apps or interfaces. Location data about users who call for help should be transmitted readily to emergency responders.</p><p>Emergency responders should have the ability to transmit this location data to SDOT to allow traffic managers to prioritize response routes.</p><p>For vehicles that require operators, all mobility service providers should:</p><p>•	Provide the user with the identity of the vehicle operator (even if the vehicle is operated remotely)</p><p>•	Inform the user if the vehicle is operated by AI</p><h4><strong>Customer service</strong></h4><p>All providers should give their users the ability to submit complaints to SDOT about their service or about the transportation network.</p><h4><strong>System reporting</strong></h4><p>All providers should report on the following</p><ul><li>Total carbon generation/savings from all their users</li><li>Equity outcomes</li><li>Security audits (such as <a href="https://www.imperva.com/learn/data-security/soc-2-compliance/">SOC 2.0</a> )</li><li>Anonymization protocols</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/288/1*_EkVcCTH8ClrNAeV7DRqRg.png" /></figure><h3>Further Considerations</h3><p>As municipal DOTs pursue technologies, they must also focus on:</p><ul><li><strong>Building robust, flexible, and reliable infrastructure</strong>. Data and information systems are critical business assets, essential to managing the right of way successfully. SDOT should avoid technology that could lock the department into proprietary systems. The technology components should be robust, able to function in times of crisis and high demand, and reliable. Data acquisition systems must be evaluated, refined, and improved continually. (This assumes the provision of adequate resource, including staff.) Data validation protocols should be built into the systems and processes.</li><li><strong>User-centricity</strong>. Too often systems and solutions are developed based on incomplete business needs or business needs develop without the context of the larger picture. SDOT should deploy a customer-first approach, putting the needs of users first and having those needs drive requirements. To do this, the department needs to develop a culture of user testing. This means ensuring that whenever a new information process or technology is proposed, a sample of intended users is surveyed and, if possible, observed using the new process or technology. These user tests may reveal that a different or modified solution will better meet the needs of users. Similarly, a diverse and representative group of internal and external stakeholders must inform policy development.</li><li><strong>Traveler information privacy and data securit</strong>y. All data and information generated, captured, shared, used, or stored must be held to the highest standards of privacy and security. These standards must ensure equitable protections for all. Transparency, accountability, and equity are key principles to uphold.</li><li><strong>Equitable access to transportation information</strong>. Informed by known historical inequities, especially as related to technology and information, SDOT should put in place safeguards to mitigate known inequities, and should continue to look for and mitigate newly recognized inequities.</li><li><strong>Strong partnerships</strong>. As transportation continues to evolve at a fast clip, projects must be developed with an eye to establishing and sustaining strong partnerships in the ecosystem.</li></ul><p><em>Up next: </em><a href="https://medium.com/p/e14d78835181/edit?source=your_stories_page---------------------------"><strong><em>Future needs and skillsets for city DOTs</em></strong></a></p><p><em>I drafted this plan with </em><a href="https://medium.com/u/93bd012e5141?source=post_page-----fcf6f27aa185----------------------"><em>Alex Hagenah</em></a><em>, </em><a href="https://medium.com/u/fa908e9a07d1?source=post_page-----fcf6f27aa185----------------------"><em>Sam Marshall</em></a><em>, and </em><a href="https://medium.com/u/9021d9e983b6?source=post_page-----fcf6f27aa185----------------------"><em>Mary Alyce</em></a><em> Eugene, my team mates and former colleagues when I served as the Seattle Department of Transportation’s Chief of Strategy and Innovation. (Our work was shaped by the very helpful insights and inputs from 30+ of our SDOT colleagues.)</em></p><p><em>I have the department’s permission to share the draft plan with whoever asks. Connect with me on </em><a href="https://www.linkedin.com/in/bdelapena"><em>Linked.In</em></a><em> and send me a DM and I will send you a link to the pdf and .docx copies.</em></p><p><em>Feel free to crib, copy, and steal the materials for your city.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1546e08a09ab" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A framework for transportation information infrastructure initiatives for municipal DOTs]]></title>
            <link>https://medium.com/@benjiedlp/a-framework-for-transportation-information-infrastructure-initiatives-for-municipal-dots-c660ddd45b0a?source=rss-f48e59011a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/c660ddd45b0a</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[transportation]]></category>
            <category><![CDATA[information]]></category>
            <category><![CDATA[cities]]></category>
            <category><![CDATA[infrastructure]]></category>
            <dc:creator><![CDATA[Benjamin de la Pena]]></dc:creator>
            <pubDate>Thu, 02 Jan 2020 21:57:48 GMT</pubDate>
            <atom:updated>2020-01-02T22:04:52.418Z</atom:updated>
            <content:encoded><![CDATA[<h4>This is part 18 of a serialized, draft, generic transportation information infrastructure plan meant to help municipal departments of transportation to manage the emerging urban transportation ecosystem</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EWBRWJgqs_R-oKheHuO5Lg.png" /><figcaption>(Graphic by <a href="http://www.xiolugo.com/">Xio Lugo</a> of <a href="https://story2designs.com/">Story2 Designs</a>.)</figcaption></figure><h3>Information as a critical service</h3><p>To serve the information needs and protect the interests and safety of the traveling public, <strong>DOTs have to approach information about the transportation network as a critical service</strong>, during normal operating conditions and in the face of system shocks (e.g., an earthquake or climate crisis impacts) and stressors (e.g., a spike in the number of travelers). The department has to push out reliable information in ways that the public and the providers that serve the public can use readily. This is particularly true of critical information that changes rapidly and must be delivered in real-time or near real-time.</p><p>To fulfill this new role and critical service, DOTs need to manage information and build information infrastructure that delivers accurate information where and when it is needed; in ways that work for the users and the providers.</p><h4>Internal DOT Initiatives</h4><p>Based on their city and their agency’s mission, vision, values and goals, information imperatives, and the traveler and actor information needs; and, to manage their city’s transportation network in the age of transportation information, DOTs should pursue the following initiatives:</p><p>Developing a <strong>Real-time Right of Way Conditions Map</strong> that will be built on an <strong>DOT Transportation API Strategy</strong>. The API strategy will be managed by an <strong>Information Delivery Unit</strong>. This new unit will work with the Asset Management team and the asset data owners and to formulate, implement and enforce a department-wide <strong>Data Governance Policy</strong>. The policy will include the development of and conformity to DOT data standards which will help the agency to start, expand, and/or maintain their DOT <strong>Data Library</strong>. The back end of operations also requires a <strong>DOT Supply Inventory</strong> system, which will be a key building block and requirement for a <strong>Mobile Digital Workforce Initiative</strong>. The Digital Workforce will also be supported by a <strong>Future Right of Way Conditions Map</strong>.</p><p>Four additional projects are critical to building out any DOT’s transportation information infrastructure: the <strong>Urban Goods Delivery Initiative</strong>; <strong>Open311 or similar</strong>; <strong>Right of Way Sensing and Beacon Infrastructure</strong>; and, <strong>Machine Learning and Predictive ROW AI</strong>.</p><p>We explain each of the initiatives and projects below¹:</p><h4><strong>1. The Real-Time Right of Way Conditions Map</strong></h4><p>Most municipal DOT’s current right of way maps are built on GIS and database technology that handles static data well but struggles when data needs to be constantly updated, especially in real-time.</p><p>DOTs need to build a right of way map that handles dynamic (constantly changing) information, published in real-time to a web-based (web-native) map platform such as Open Street Map or SharedStreets (which is built on Open Street Map). The goal is to have data feeds and APIs that other providers can use through machine-to-machine (or system-to system) information flows.</p><p>This would be separate from the existing right of way map that usually locates all of a municipal DOT’s (and the city’s) fixed assets on the right of way.²</p><p>The Real-time Right of Way Conditions Map should include:</p><ul><li>Real-time traffic conditions</li><li>Real-time bus and rail routes</li><li>Real-time locations of high-capacity transit</li><li>Real-time shared-vehicle availability</li><li>Real-time sidewalk, road and bridge closures</li><li>Real-time locations of urban deliveries</li><li>Real-time parking availability</li></ul><p><em>The Real-time Right of Way Conditions Map will be built on a DOT Transportation API Strategy.</em></p><h4><strong>2. The DOT Transportation I/O (DOT’s transportation API strategy)</strong></h4><p>To deliver on the information needs of the Real-time Right of Way Conditions Map listed above and to provide information that can be ingested in real-time by transportation information and service providers, a municipal DOT needs to build a coherent, enterprise-level strategy of pushing data out and taking data in via APIs and data feeds.</p><p><strong>The Real-time Right of Way Conditions Map and the transportation API strategy need to provide information that is accessible and easily portable or interpreted into channels that do not require the traveling public to use personal devices or payment or subscription to internet access.</strong></p><p><em>A DOT’s transportation API strategy needs to be managed by a DOT Information Delivery Unit.</em></p><h4><strong>3. The DOT Information Delivery Unit</strong></h4><p>The Information Delivery Unit (IDU) will be tasked with implementing the municipal DOT Transportation API Strategy and the build out of the Real-time Right of Way Conditions Map. The IDU will set out information delivery standards (up time, data specs, etc.) for all data and information the department shares via API data feeds. The unit will manage or oversee the projects to deliver each API. It will be accountable for usability, dependability and performance of the APIs. It will be accountable for the information imperatives set forth in this plan and ensure that the systems that deliver the APIs and data feeds are resilient.</p><p>The IDU will coordinate the city’s Information Technology Department (if any) and with the asset owners and the divisions responsible for the real-time data that will feed the APIs.</p><p>The IDU will work with the DOT’s other units, and particularly with:</p><ul><li>transportation operations for approved traffic control plans, and signs and signals</li><li>maintenance operations for maintenance road closures, incidents and customer complaints</li><li>capital projects design and delivery for capital project schedules</li><li>Bridge and other structures for bridge status and conditions</li><li>street use and/or the permit desk for permitted road closure schedules</li><li>transit and mobility operations for fixed routes and new mobility service providers</li><li>policy and planning, and project planning for plans and the informational requirements of planned infrastructure</li><li>asset management for asset locations, conditions and inventories</li><li>communication for automated notices</li></ul><p>The IDU could be housed under the DOT’s transportation (traffic) operations unit and, in coordination with a data librarian, should maintain the DOT’s data inventory.</p><p>Working with transit and mobility operations, the IDU will also set standards and performance agreements for incoming API and data feeds from information and mobility service providers.</p><p>The IDU will work with the asset managers and the asset data owners and to formulate, implement and enforce a new Data Governance Policy and to maintain the DOT’s Data Library.</p><h4>4. Data governance policy</h4><p>The municipal DOT, in consultation with the its city IT department, will set rules for the handling of transportation data. The policy will be shaped by their city’s privacy principles, surveillance ordinance, and mobility data management policies.</p><p><strong>The policy will set the frame and goals for addressing equity issues concerning data collection, use and distribution.</strong></p><p>The policy will set accountability for managing DOT datasets, including protocols for upkeep, validation, testing, and archiving. <strong>It will set data integrity and data delivery as key performance indicators for asset and program owners.</strong> It will set reporting requirements for dataset owners.</p><p>In coordination with the city IT, the policy will reinforce the rules on handling personally identifiable information in all DOT datasets, APIs, and data feeds.</p><p><strong>The policy will require all completed DOT capital projects (whether delivered by contractors or by crews) to deliver digital records of the as-built assets upon turnover</strong>. It will ensure the reporting of completed asset information to help track the DOT’s commitments.</p><p><em>The digital records will conform to the DOT’s data standards, if available, so that the records can readily be uploaded to a DOT asset inventory and data library.</em></p><h4>5. DOT Data Library</h4><p>The DOT Data Library will be the standardized central catalog of all the data that DOT collects. The Data Library will make it easier to find, understand, and use DOT data. The Data Library serves two primary purposes:</p><ul><li>Centralized, managed access to all data and metadata.</li><li>Continuous data monitoring</li></ul><p>In conjunction with the Data Governance Policy, the Data Library will ensure that the municipal DOT standardizes the way it collects and maintains information and assures that DOT staff have access to, and can provide the public with, the most up-to-date information and analysis.</p><h4>6. Updated and validated asset inventory</h4><p>A municipal DOT’s digital records of its physical assets must reflect accurately the assets on the ground. DOTs should invest resources in updating and maintaining their asset inventory so that there are minimal discrepancies between what is in their records and what is built.</p><p>An up-to-date and validated physical asset inventory reduces risks and mitigates possible liabilities for a DOT when issues of information availability and validity arise.</p><p>The updated and validated asset inventory will deploy protocols to ensure accurate data is uploaded to the inventory upon delivery of private construction and crew built capital projects. All assets deployed in the transportation network must be geolocated, and this information carried in the asset inventory.</p><p><em>Particularly for crew-delivered projects, the asset inventory must rely on the DOT supply inventory.</em></p><h4>7. DOT supply inventory</h4><p>A DOT needs to deploy and maintain a supply inventory, particularly for physical objects in its transportation infrastructure (e.g., signs, signals, and signal components). The supply inventory will help a DOT to track the locations of fixed and interchangeable assets it deploys and maintains.</p><p>The supply inventory will automate geolocating assets and will facilitate inspection, maintenance, and repair work.</p><p><em>The supply inventory is a key building block for a DOT’s Mobile Digital Workforce Initiative.</em></p><h4>8. Mobile digital workforce initiative</h4><p>A DOT should invest in tools that allow DOT crews and project personnel to access and deliver information while in the field. This includes the status of repair work and capital work, the conditions of existing assets, and findings from inspections. It includes digital notifications of emergency road closures, asset attribute changes, and real-time information on incidents</p><p>The mobile digital workforce initiative will equip DOT staff (particularly crews, project and construction managers, and inspectors) with the application environment (software) and hardware (phones and tablets) they need to gather, transmit, receive, and update information<em> in situ</em>. This assures that the DOT has the latest information about conditions in the right of way. This includes purchasing or developing a suite of software tools that are mobile from the ground up (built for phones or tablets) that interface with a DOT’s existing right of way map (for assets) and the proposed real-time right of way conditions map.</p><p><em>The Mobile Digital Workforce initiative will be supported by a Future Right of Way Conditions Map.</em></p><h4>9. Future Right of Way Conditions Map</h4><p>Municipal DOTs need a map to display the future (planned or permitted) conditions of the right of way. For most DOTs, this information is usually distributed in various databases or GIS datasets and files, or in documents. As with the Real-time Right of Way Map, the goal is to have data feeds and APIs that other providers can use through machine-to-machine (or system-to system) information flows.</p><p><strong><em>a) Traffic Control Plans (TCP) on Map</em></strong></p><p>Depending on the size of and growth rate of the city, DOTs receive and process dozens of traffic control plans (TCPs) each week. These plans are often submitted as paper or PDF (or scanned PDF) files. Each plan must be reviewed against existing traffic configurations and TCPs for previously approved plans. The process is tedious and intensive. Accessing the TCPs is usually still a manual process of looking through various digital files.</p><p>The TCP on Map project will shift TCP submissions so they begin with locating the project on a web-based but access-restricted map and schedule. The applications and plans should then be accessible via the web map, with the elements of the control plans (lane and sidewalk closures, sign placements, etc.) viewable from the map itself.</p><p>The TCP on Map project will provide DOT staff with easily accessible situational information on current and future permitted road closures.</p><p><strong><em>b) Plans on Map</em></strong></p><p>DOTs usually publish their plans (modal plans, district plans and implementation plans) as downloadable online publications or as topical websites. To illustrate the plans, the publications and/or the websites include map graphics. The map graphics are flat images that may be partially interactive. The maps are usually created on a GIS-generated base map and may be stored as GIS files.</p><p>The Plans on Map project will deliver these plans on a web-based map. The map-based interface will allow the public and stakeholders to view any plan situated in the geography and in spatial relation to other plans.</p><p>DOTs will need to determine at what stage of the planning process the plans should appear on the map or develop a convention to indicate what stage a plan is in.</p><p><strong><em>c) Capital Projects on Map</em></strong></p><p>Future DOT construction projects, whether contractor or crew-delivered, should be available on a map with as much detail as is possible, including data on construction and road closure schedules.</p><p>The TCP on Map, Plans on Map, and Capital Projects on Map projects would constitute the core of a web-based Future Right of Way Conditions Map that will allow customers and stakeholders to understand how the DOT is shaping and managing the future of the city’s right of way and transportation network.</p><p><em>Four additional projects are critical to building out a municipal DOT’s transportation information infrastructure:</em></p><h4><strong>10. Urban goods delivery data initiative</strong></h4><p>Urban goods delivery is, by some accounts, the fastest growing segment of the transportation system.³ This includes e-commerce deliveries to homes and businesses, and grocery and restaurant deliveries. Data-wise, this segment is highly integrated across the supply chain. The online ordering systems connect directly to order fulfillment and delivery systems. The customer can know the predicted day and time of the delivery and can confirm delivery even remotely.</p><p>This information is critical to managing the transportation system. Current, historic and predictive data can help DOTs manage traffic more effectively along arteries and in urban centers and villages.</p><h4><strong>11. Open311</strong></h4><p>Open31⁴ or a similar open data protocol for requests will allow DOTs to exchange information with other government units using the Open311 standard. It will improve the flow of information around customer complaints and road closures by making the information exchange all digital.</p><p>Open311 or a similar protocol will feed into a DOT’s APIs and be incorporated into the Real-time Right of Way Conditions Map to track the agency’s response.</p><h4>12. Right of way sensing and beacon infrastructure</h4><p>To determine traffic flow, speeds and congestion, most DOTs have deployed various sensing device,⁵ including WiFi sensors and license-plate readers, in specific areas of the transportation network. The data these sensors produce is critical to assessing and analyzing the flow of traffic.</p><p>DOTs need to expand and continue investing in (and maintaining) their sensor networks, and invest in additional real-time sensors that provide information on:</p><ul><li>Pedestrian and public-life counters</li><li>Bike and micro-mobility counters</li><li>Public transit stations (wait times and volumes of passengers)</li><li>traffic flow on arterials</li></ul><p>DOTs should consider investing in wireless beacons to broadcast the location of infrastructure such as</p><ul><li>Arterials</li><li>Bus stops</li><li>Load zones</li></ul><p>As with the WiFi sensors and the license-plate readers, DOTs should follow a strict protocol to protect privacy so that the data from these sensors are not used for unauthorized surveillance.⁶</p><p><em>The data from these sensors, combined with the data from APIs (displayed on the Real-time Right of Way Conditions Map) will allow a municipal DOT to employ machine learning and predictive right of way AI.</em></p><h4>13. Machine learning and predictive right of way AI</h4><p>Ideally, DOTs should leverage the transportation information they generate and receive by deploying machine learning to get a deeper sense of the traffic and transportation patterns of the city. The information and data could help develop a predictive algorithm (AI) for right of way conditions.</p><p>The predictive algorithms should be explainable and transparent. The development should be guided by the city and the DOTs shared values and by the information imperatives set forth in this plan. The algorithms should help a DOT set forth further policies to a) accelerate decarbonization; 2) advance equity; 3) protect privacy; and, sustain markets.</p><h4>Special Attention to Information Accessibility</h4><p>The city’s transportation information infrastructure must provide for the needs of all travelers, including those who may have special challenges or may not have adequate access to information. DOTs should develop a standard tools, akin to the Seattle’s Racial Equity Toolkit (RET) to evaluate the accessibility of transportation information across modes and demographics.</p><p>The tools should be used to look at current conditions and identify opportunities for improvements, as well as to evaluate proposed projects that may impact the information ecosystem. The tools should include:</p><ul><li>an assessment of how connectivity issues affect information delivery to travelers;</li><li>an assessment looking at user-specific issues (e.g., vision or hearing impairment), both under current conditions and any previous conditions where connectivity issues have been addressed; and,</li><li>a guide to creating an action plan to address both connectivity and user-specific access issues identified in the preceding sections.</li></ul><p><em>References:</em></p><ol><li><em>The numbering of this section does not imply prioritization or sequencing. Instead it is about how each initiative fits with the others.</em></li><li><em>Seattle’s example of </em><a href="https://www.seattle.gov/transportation/permits-and-services/interactive-maps"><em>available online maps are available here</em></a><em>.</em></li><li><em>See International Transport Forum’s “Towards Road Freight Decarbonisation: Trends, Measures and Policies,” (2018).</em></li><li><em>More information on </em><a href="http://www.open311.org/learn/"><em>Open311 here</em></a><em>.</em></li><li><em>We’ve deployed magnetometers that count vehicle volumes and in select locations, bike volumes. We use cameras to detect vehicles waiting at stoplights and are starting to use them to also track volumes, speeds, and vehicle type. We use pneumatic tubes for volume, speed, and classification studies (for vehicles and bicycles). We even have infrared beams that count pedestrians. We use portable cameras for automated turning movement counts and other traffic studies.</em></li><li><em>There are serious privacy concerns about the use of Bluetooth beacons. Beacons are “dumb” infrastructure that simply broadcast their location data, which can be picked up by sensors in phones and other devices to help in geolocation. They do not and cannot pull or store any data. However, apps using the beacon data can locate the travel patterns of individuals.</em></li></ol><p><em>Up next: </em><strong><em>Ecosystem policy directions and further considerations</em></strong></p><p><em>I drafted this plan with </em><a href="https://medium.com/u/93bd012e5141?source=post_page-----fcf6f27aa185----------------------"><em>Alex Hagenah</em></a><em>, </em><a href="https://medium.com/u/fa908e9a07d1?source=post_page-----fcf6f27aa185----------------------"><em>Sam Marshall</em></a><em>, and </em><a href="https://medium.com/u/9021d9e983b6?source=post_page-----fcf6f27aa185----------------------"><em>Mary Alyce</em></a><em> Eugene, my team mates and former colleagues when I served as the Seattle Department of Transportation’s Chief of Strategy and Innovation. (Our work was shaped by the very helpful insights and inputs from 30+ of our SDOT colleagues.)</em></p><p><em>I have the department’s permission to share the draft plan with whoever asks. Connect with me on </em><a href="https://www.linkedin.com/in/bdelapena"><em>Linked.In</em></a><em> and send me a DM and I will send you a link to the pdf and .docx copies.</em></p><p><em>Feel free to crib, copy, and steal the materials for your city.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c660ddd45b0a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Requirements for City DOT Functions]]></title>
            <link>https://medium.com/@benjiedlp/requirements-for-city-dot-functions-e02cfb272f8b?source=rss-f48e59011a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/e02cfb272f8b</guid>
            <category><![CDATA[cities]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[transportation]]></category>
            <category><![CDATA[infrastructure]]></category>
            <category><![CDATA[information]]></category>
            <dc:creator><![CDATA[Benjamin de la Pena]]></dc:creator>
            <pubDate>Wed, 01 Jan 2020 18:21:01 GMT</pubDate>
            <atom:updated>2020-01-01T18:21:01.205Z</atom:updated>
            <content:encoded><![CDATA[<h4>This is part 17 of a serialized, draft, generic transportation information infrastructure plan meant to help municipal departments of transportation to manage the emerging urban transportation ecosystem</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*heIsrN_QXvvHVaJo67z7Xw.png" /><figcaption>(Graphic by <a href="http://www.xiolugo.com/">Xio Lugo</a> of <a href="https://story2designs.com/">Story2 Designs</a>.)</figcaption></figure><p>We identified seven functional roles in SDOT that are relevant to our ability to deliver information to the traveling public and to the other actors in the ecosystem. The functions are:</p><ul><li><strong>DOT traffic managers</strong> <strong>and traffic control planners</strong> are staff who manage the transportation network and respond to the conditions in real-time, hourly, daily, weekly or monthly</li><li><strong>DOT maintenance managers</strong> are staff who maintain the transportation infrastructure (including urban forestry) and respond hourly, daily, weekly or monthly to the conditions.</li><li><strong>DOT curb use and parking managers</strong> are staff who manage parking, load zones and other uses of the curb</li><li><strong>DOT transportation planners and mobility program managers</strong> are staff who manage mobility programs and plan the transportation infrastructure and services for the next three to five years or longer</li><li><strong>DOT project and construction managers</strong> are staff who design, manage and build transportation projects</li><li><strong>DOT street use (street permit) managers</strong> are staff who permit and regulate activities on the right of way</li><li><strong>DOT asset owners </strong>are staff who are accountable for certain classes of physical assets (for example, sidewalks or bridges). This includes staff responsible for maintaining data about these assets.</li></ul><p>To deliver the user needs enumerated above, we developed a list of information needs for each function. These needs also come in the form of user requirements.</p><p>For example, we might say:</p><p><strong>As DOT traffic managers, we need …</strong></p><ul><li>…near-term (next day and day after) scheduled road closures or road work on arterials</li></ul><p>Or</p><ul><li>…advance notice (30 minute to one hour) of emergency road maintenance work on arterials</li></ul><p>This is a list of both current and aspirational needs. Most DOTs are already collecting some or most of the requirements. There are requirements DOTs may want to collect but current technology or infrastructure does not yet allow them to do so.</p><p>The information needs for each function are listed below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0-2p08yom6CMvoGu9tI_oQ.png" /><figcaption>(Graphic by <a href="http://www.xiolugo.com/">Xio Lugo</a> of <a href="https://story2designs.com/">Story2 Designs</a>.)</figcaption></figure><h3><em>Information needs of DOT functions</em></h3><h4>DOT traffic managers and traffic control planners need…</h4><ol><li>…near-term (next day and day after) notice of scheduled road closures or road work on arterials</li><li>…advance notice (30 minutes to one hour) of emergency road maintenance work on arterials</li><li>…real-time information on pedestrians, cyclist and vehicle volumes and speeds on arterials</li><li>…historical and predicted data on volumes and speeds on arterials</li><li>…historical and predicted data on high-crash and near-miss locations on arterials</li><li>…real-time information on sudden volume spikes or unexpected congestion on non-arterials</li><li>…real-time information on the status of locations, routes and schedules of high-capacity transit (buses and trains)</li><li>…historic speed and reliability data on high-capacity transit (buses and trains)</li><li>…real-time information on re-routes</li><li>…reports and real-time information on incidents and emergencies on arterials and non-arterials</li><li>…near-term (next day and day after) predicted routes for freight deliveries (commercial and residential)</li><li>…to be able to trust (verified and validated) the information and the sources of the information above</li><li>…to be able to differentiate the above information into data about arterials and non-arterials</li><li>…a way to inform users of the status of incidents and road closures (real-time and future)</li><li>…a way to inform decision makers and city leaders on current state of the system, particularly of emergencies or unexpected congestion</li><li>…information about permitted road closures, including schedule and impact</li><li>…information about submitted requests for permits for road closures, including schedule and impact</li><li>…information about traffic control plans (TCPs) for events and road closures</li><li>…to know future plans for streets and corridors</li><li>…all the above information in open standard, interoperable, and usable data formats that don’t tie us down to any single software service or platform</li></ol><h4>DOT maintenance managers need…</h4><ol><li>…a warehouse inventory system so we can track in real-time the status of all our supplies, equipment, and materials and to geolocate all our fixed and non-fixed assets</li><li>…to create work orders, with exact locations geolocated, and send them out digitally to work crews</li><li>…to get automatically geolocated asset serial numbers attached to work orders</li><li>…the ability to close a work order, with exact locations geolocated, from the site upon the completion of the job (this includes updating the asset inventory upon job completion)</li><li>…to send out geolocated information automatically on current and future planned maintenance work (including urban forestry work)</li><li>…to send out geolocated information automatically on sidewalk and road closures for emergency maintenance work (including urban forestry work)</li><li>…to get accurate and verified information on the location and condition of assets and repair needs, including trees and sidewalks (and sidewalk elements)</li><li>…to receive geolocated customer complaints and requests (tied to physical asset inventories)</li><li>…to send back responses and status updates to customer complaints and requests</li><li>…to get real-time information on pedestrians, cyclist and vehicle volumes and speeds and speeds in areas where repair and maintenance work is scheduled</li><li>…to get information about current and future permitted road closures, including schedule and impact</li><li>…to receive information on prioritization of maintenance work/projects</li><li>…to receive and send out notifications on emergency and incident response and status</li><li>…to report in real-time the completion of maintenance work and resumption of traffic flow or opening of sidewalk</li><li>…to send/record time-stamped, geolocated information on the work completed (what was done to which asset, where)</li><li>…to get annual (or even monthly) pedestrian volume counts along all (or most) sidewalks, to help inform the prioritization of sidewalk maintenance where pedestrian volumes are higher</li><li>…to be able to issue a citation from the field, with the ability to attach photos and have the document geolocated, for violation of street tree ordinance or permit requirements</li><li>…all the above information in open standard, interoperable, geolocated, and usable data formats that don’t tie us down to any single software service or platform</li></ol><h4><strong>DOT curb and parking managers need…</strong></h4><ol><li>…to send current curb, load zone and parking information to operators and the traveling public</li><li>…to send out new curb, parking and load zone rates, rules and schedules, automatically (and geolocated)</li><li>…to receive real-time curb use location and use data from mobility service operators (e.g., TNCs or delivery vehicles)</li><li>…to send out geolocated information on fees and charges, with schedules and rates</li><li>…to receive information on parking or load zone violations</li><li>…to receive customer inquiries, complaints or reports</li><li>…to receive aggregated data on use of curb, parking and load zones</li><li>…to send updates regarding our on-street assets like pay stations and signs</li><li>…all the above information in open standard, interoperable, and usable data formats that don’t tie us down to any single software service or platform</li></ol><h4>DOT transportation planners and mobility program managers need…</h4><ol><li>…aggregated, anonymized, and validated historical performance data on all SDOT and other government transportation assets (roads, bridges, bike lanes, etc.) and should include curb uses, public life, pedestrian counts, etc.</li><li>…the predicted usage growth rates for all DOT and other government transportation assets</li><li>…the predicted growth rates and conditions of existing and new DOT and other government transportation assets based on funding trends and current conditions</li><li>…current and predicted development patterns, including building and demographic data</li><li>…aggregated, anonymized, and validated historical performance data from all mobility service operators (light rail, ferry, bus, shuttle, bike-share, e-scooters, TNCs, etc.)</li><li>…predicted growth rates and use of all mobility service operators by geographic area</li><li>…reports on equity outcomes and current conditions for key DOT and other government transportation assets</li><li>…reports on carbon generated (historic and current) for all DOT and other government transportation assets</li><li>…reports on carbon generated (historic and current) for mobility service operators</li><li>…infrastructure and investment plans from other government transportation agencies</li><li>…post-project completion performance data for all DOT and other government transportation assets</li><li>…to publish and disseminate to the public draft and final plans</li><li>…to receive questions and comments from public and stakeholders on plans</li></ol><h4>DOT project and construction managers need…</h4><ol><li>…to receive validated current-state and historical performance data on DOT assets (roads, bridges, bike lanes, curb uses, public life, pedestrian counts, etc.)</li><li>…to automatically input project schedules and impacts to publicly accessible map based system (such as dotMaps) -this data should integrate with our other information systems</li><li>…to publish draft and final plans for each project</li><li>…to receive questions and comments on draft and final plans</li><li>…to notify other DOT divisions/units of project schedules, timing and impacts</li><li>…to submit proposed traffic control plans (mapped and geolocated)</li><li>…to receive approval of proposed traffic control plans (mapped and geolocated)</li><li>…to receive information on traffic control plans and re-routes</li><li>…to receive schedules and locations of planned road closures and other events that will affect construction</li><li>…to send out real-time or near real-time (one-hour delay) notifications on the status of construction projects, including traffic impacts</li><li>…to receive short-term notifications of maintenance work</li><li>…to notify the public and adjacent property owners in real-time of project schedules, road closures, re-routes and other impacts</li><li>…to release above information in multiple languages</li><li>…to receive and respond to questions, reports and complaints</li><li>…to report job completion to relevant project managers and update construction coordination and asset inventory systems</li><li>…to report project delivery status, accomplishments and performance data</li><li>…to share network files and access across other city departments</li><li>…to share software/system licensing across city departments</li><li>…to receive information monthly on actual expenditures for projects</li><li>…to be able to stay up to date with project management software technology</li><li>…to be able to submit work orders with a tracking system for work on capital projects that is to be performed by city crews</li><li>…to be able to prepare a single update report instead of reporting updates multiple times through multiple channels</li><li>…to have our project management systems build in the conditions and reminders about the specifics of each grant used on a project</li><li>…to report project status to financial managers and grant sources (if relevant)</li></ol><h4><strong>DOT street use (street permit) managers need…</strong></h4><ol><li>…to send out permitting rules and fee schedules</li><li>…to receive permit requests and plans including predicted transportation impacts (road and sidewalk closures, etc.)</li><li>…to send out real-time status of permit requests to applicants</li><li>…to determine conflicts in permits, activities, and events automatically</li><li>…to send out approved/permitted requests and plans including approved traffic control plans and re-routes</li><li>…to send out geolocated and mapped information about requests including approved traffic control plans and re-routes</li><li>…to send out geolocated and mapped information about permitted activity</li><li>…to receive questions, reports and complaints</li><li>…information on the status of the response to questions, reports and complaints</li><li>…to report and validate violations (mapped and geolocated) and to identify code and permit violations in the field in real-time</li><li>…to notify the public of schedules, road closures, and re-routes</li><li>…to update the system of record (official database) automatically</li><li>…to update asset infrastructure when changes are made by private development</li><li>…to receive and validate payments</li><li>…to report remotely on inspections of permitted work</li><li>…to route plans electronically for review by secondary reviewers inside and outside the city firewall</li><li>…to understand the allowed uses of the right of way in real-time, including temporary closures. This should include the locations of all permitted encroachments (and ideally un-permitted encroachments as well).</li><li>…to know the location of all infrastructure buried in the right of way and above it; including information about that infrastructure (voltage of power lines in conduits, etc.)</li><li>…to provide estimated time frames for review</li><li>…to send out inspection reports electronically</li><li>…to record and manage time spent at any one job site</li><li>…to update the future inspection schedule based on inspection results and inform contractors of upcoming inspections</li><li>…to track final inspections and notify affected partners of asset improvements and changes</li></ol><h4>DOT asset managers need…</h4><ol><li>…an updated and validated list of assets in the right of way</li><li>…a process to update the inventory with assets that are in the right of way but not in the database</li><li>…a process to make sure all new assets are included correctly, with location data, in the asset inventory database</li><li>…a process or systems to allow us to update the asset inventory from the field, with geolocation</li><li>…a regular audit of assets to make sure our inventory is trustworthy</li></ol><p><em>Up next: </em><strong><em>A framework for information infrastructure initiatives for municipal DOTs</em></strong></p><p><em>I drafted this plan with </em><a href="https://medium.com/u/93bd012e5141?source=post_page-----fcf6f27aa185----------------------"><em>Alex Hagenah</em></a><em>, </em><a href="https://medium.com/u/fa908e9a07d1?source=post_page-----fcf6f27aa185----------------------"><em>Sam Marshall</em></a><em>, and </em><a href="https://medium.com/u/9021d9e983b6?source=post_page-----fcf6f27aa185----------------------"><em>Mary Alyce</em></a><em> Eugene, my team mates and former colleagues when I served as the Seattle Department of Transportation’s Chief of Strategy and Innovation. (Our work was shaped by the very helpful insights and inputs from 30+ of our SDOT colleagues.)</em></p><p><em>I have the department’s permission to share the draft plan with whoever asks. Connect with me on </em><a href="https://www.linkedin.com/in/bdelapena"><em>Linked.In</em></a><em> and send me a DM and I will send you a link to the pdf and .docx copies.</em></p><p><em>Feel free to crib, copy, and steal the materials for your city.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e02cfb272f8b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[User stories and user requirements for transportation information]]></title>
            <link>https://medium.com/@benjiedlp/user-stories-and-user-requirements-for-transportation-information-775a9021f185?source=rss-f48e59011a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/775a9021f185</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[information]]></category>
            <category><![CDATA[transportation]]></category>
            <category><![CDATA[infrastructure]]></category>
            <category><![CDATA[cities]]></category>
            <dc:creator><![CDATA[Benjamin de la Pena]]></dc:creator>
            <pubDate>Tue, 31 Dec 2019 18:44:38 GMT</pubDate>
            <atom:updated>2019-12-31T18:44:38.685Z</atom:updated>
            <content:encoded><![CDATA[<h4>This is part 16 of a serialized, draft, generic transportation information infrastructure plan meant to help municipal departments of transportation to manage the emerging urban transportation ecosystem</h4><h3>User Stories</h3><p>These are the user stories we generated using the traveler personas’ needs and protections, and using the <a href="https://link.medium.com/a0b5z2HdS2">four information imperatives</a>.</p><p>(As the transportation system evolves, user stories may change, as might the degree to which user needs are satisfied. DOTs should continue to reevaluate these stories against the current technologies and the state of the system.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AIr7lzObYxVgOxwN-7f6JA.png" /><figcaption>(Graphics by <a href="http://www.xiolugo.com/">Xio Lugo</a> of <a href="https://story2designs.com/">Story2 Designs</a>.)</figcaption></figure><p><strong>As a TRAVELER USING THE TRANSPORTATION SYSTEM:</strong></p><h4><em>To help accelerate de-carbonization</em><strong><em>, I need to know …</em></strong></h4><ul><li>…how much carbon a travel option (or a delivery) will generate or save.</li></ul><h4><em>To advance equity, I need to know…</em></h4><ul><li>…that I am not being discriminated against because of my age, race, gender identity, sexual orientation, disability, ethnicity, nationality, or religion; and,</li><li>…that the information is available to me in ways that don’t require a personal smartphone or an internet account.</li></ul><h4><em>To protect my privacy</em>, I need to know…</h4><ul><li>…that my private information, my travel patterns and my location data will not be used for profit or resold without my express consent; and,</li><li>…that the data or information I generate or is generated about me is not used for surveillance purposes without legal authorization.</li></ul><h4><em>To ensure a level playing field</em>, I need to know…</h4><ul><li>…all the transportation options and services available to me at each stage of the journey; and,</li><li>…the comparative costs (in $) of the travel option or delivery service I am using or will use.</li></ul><h3>On location and navigation information</h3><p><strong>As a TRAVELER USING THE TRANSPORTATION SYSTEM, I need to know …</strong></p><ul><li>…the best or recommended route to my destination (this includes the conditions of the physical infrastructure along the route);</li><li>…the exact location of transportation options (stations, parking locations, etc.) relative to my location;</li><li>…how to connect to another travel mode if I need to; and,</li><li>…the locations of parking spaces, load zones, boarding and hailing zones, stations, and where to wait for a vehicle.</li></ul><h3>On notification and status information</h3><p><strong>I need to know …</strong></p><ul><li>…the current state of sidewalks, roads, routes, and schedules (this should include current traffic, wait times and passenger volumes and this information must be accurate and dependable);</li><li>…if there are sidewalk and road closures, changes in schedules or routes that will affect my trip;</li><li>…how many parking slots are available (car, bike or scooter, etc.); and,</li><li>…If there are areas or routes where the mode or vehicle I am taking is prioritized or is not allowed.</li></ul><h3>On reporting and safety information</h3><p><strong>I need to know …</strong></p><ul><li>…who is operating the vehicle (if it’s not me) and that I can trust them, and if it is run by a human or by AI;</li><li>…how to (and be able to) report conditions that affect my trip; and,</li><li>…how to (and be able to) request for help for emergencies.</li></ul><h3>On payment information</h3><p><strong>I need to know …</strong></p><ul><li>…how to pay for my trip if there are any fees, fares or tolls required (and how I will be refunded for failures in service);</li><li>…if there are incentives or restrictions; and,</li><li>…that there are other ways to pay for fares or fees if I don’t have a credit card, a smartphone or internet access.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0-2p08yom6CMvoGu9tI_oQ.png" /><figcaption>(Graphic by <a href="http://www.xiolugo.com/">Xio Lugo</a> of <a href="https://story2designs.com/">Story2 Designs</a>.)</figcaption></figure><h3>Requirements for actors in the transportation information ecosystem</h3><p>Based on the user needs enumerated above, we generated a list of information needs for the actors in the ecosystem. We set out three categories of actor: 1) emergency responders; 2) information and mobility service providers; and, 3) DOTs.</p><p>(We used the requirements for DOTs to include requirements from other government agencies.)</p><p>The information needs of the actors are listed below.</p><h3>Emergency responders</h3><p><strong>As an EMERGENCY RESPONDER, I need …</strong></p><ul><li>…a way to receive emergency requests with location information;</li><li>…to know the current state of roads, routes, and schedules (this information must be accurate and dependable);</li><li>…to know the best possible or prioritized route to the incident and to hospitals (this information must be accurate and dependable);</li><li>…a way to inform others of our estimated time of arrival to an incident;</li><li>…to know if there are road closures, changes in schedules or routes that will affect the emergency response;</li><li>…to know what other services are responding;</li><li>…a way to inform other responders of the status of the emergency;</li><li>…a way to inform traffic managers of the status of the emergency;</li><li>…a way to warn other travelers to avoid the area where there is an emergency response;</li><li>…a way to record the status and conditions of the emergency and the response;</li><li>…a way to inform traffic managers of what route I am going to take so they can prioritize that route; and,</li><li>…a way to digitally inform the traffic managers in real-time that emergency services are closing a road segment, sidewalk or loading zone for incident response.</li></ul><h3>Information or mobility service providers</h3><p><strong>As an INFORMATION OR MOBILITY SERVICE PROVIDER, I need …</strong></p><ul><li>…the most current infrastructure maps and plans;</li><li>…to know the current and future state of roads, routes, and schedules, including current traffic and volumes (this information must be accurate and dependable);</li><li>…real-time, validated information on traffic lights, speed limits, and other road or mobility rules;</li><li>…to know if there are current or future road closures, changes in schedules or routes that will affect anyone who uses my service;</li><li>…to know the locations of parking spaces, load zones, drone docks or parking, boarding and hailing zones, transit and bus stations, charging infrastructure, and wait zones;</li><li>…to know the schedules of parking spaces, load zones, drone docks or parking, boarding and hailing zones, transit and bus stations, and where to wait for a vehicle or a rider;</li><li>…accurate and verified information from traffic managers on current and historical transportation data;</li><li>…accurate and verified information from transportation planners on future plans for transportation;</li><li>…access to accurate and verified data from other information service operators and from mobility service operators;</li><li>…the most current (and applicable) versions of relevant policies and rules;</li><li>…the most current fee and fare schedules for my service and for other available services;</li><li>…the rules for autonomous vehicles and drones;</li><li>…to be notified of any changes in policies and rules;</li><li>…to be notified of any changes in fee and fare schedules;</li><li>…to be able to report conditions that affect the experience of my customers and my service;</li><li>…to be able to request for help for emergencies;</li><li>…to assure my customers/the users of my service that they can trust my service with their data: (a) that I will not resell it without their express consent; (b) that I will not use it for surveillance; and,</li><li>…all the above information in open standard, usable data formats that don’t tie me down to any single software service or platform.</li></ul><p><em>Up next: </em><strong><em>Requirements for DOT functions</em></strong></p><p><em>I drafted this plan with </em><a href="https://medium.com/u/93bd012e5141?source=post_page-----fcf6f27aa185----------------------"><em>Alex Hagenah</em></a><em>, </em><a href="https://medium.com/u/fa908e9a07d1?source=post_page-----fcf6f27aa185----------------------"><em>Sam Marshall</em></a><em>, and </em><a href="https://medium.com/u/9021d9e983b6?source=post_page-----fcf6f27aa185----------------------"><em>Mary Alyce</em></a><em> Eugene, my team mates and former colleagues when I served as the Seattle Department of Transportation’s Chief of Strategy and Innovation. (Our work was shaped by the very helpful insights and inputs from 30+ of our SDOT colleagues.)</em></p><p><em>I have the department’s permission to share the draft plan with whoever asks. Connect with me on </em><a href="https://www.linkedin.com/in/bdelapena"><em>Linked.In</em></a><em> and send me a DM and I will send you a link to the pdf and .docx copies.</em></p><p><em>Feel free to crib, copy, and steal the materials for your city.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=775a9021f185" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Making transportation information accessible, safe, secure, and resilient]]></title>
            <link>https://medium.com/@benjiedlp/making-transportation-information-accessible-safe-secure-and-resilient-82790bc8ecd5?source=rss-f48e59011a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/82790bc8ecd5</guid>
            <category><![CDATA[cities]]></category>
            <category><![CDATA[infrastructure]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[transportation]]></category>
            <category><![CDATA[information]]></category>
            <dc:creator><![CDATA[Benjamin de la Pena]]></dc:creator>
            <pubDate>Tue, 31 Dec 2019 01:34:50 GMT</pubDate>
            <atom:updated>2019-12-31T01:34:50.731Z</atom:updated>
            <content:encoded><![CDATA[<h4>This is part 15 of a serialized, draft, generic transportation information infrastructure plan meant to help municipal departments of transportation to manage the emerging urban transportation ecosystem</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iLElrtIDTOYY61vWXjpchg.png" /><figcaption>(Graphic by <a href="http://www.xiolugo.com/">Xio Lugo</a> of <a href="https://story2designs.com/">Story2 Designs</a>.)</figcaption></figure><h3>Making sure transportation information…</h3><h3>…is accessible</h3><p>Travelers must be able to access information that allows them to complete their trip safely and efficiently, regardless of whether they have a smart device or internet access.</p><p>The city of Seattle conducted a <a href="https://www.seattle.gov/Documents/Departments/SeattleIT/DigitalEngagement/TechAccess/City%20of%20Seattle%20IT%20Summary_Final.pdf">Seattle Technology Access and Adoption Study</a> in 2018, the findings are particular to the city but probably reflects the situation in most other US cities.</p><p>The survey found that the percentage of Seattle households with internet access increased from 85% in 2013 to 95% in 2018. Internet-capable mobile phone ownership rose from 58% to 93% during the same period. This is an encouraging trend, but it also means that roughly 1 in 20 residents are unable to use internet-based services to plan their trip at home, and 1 in 13 residents are unable to access internet-based transportation information while traveling.</p><p>Meanwhile, one out of four (23%) Seattle residents identified “a limiting factor to not using the internet more.” Top reasons included:</p><ul><li><em>Internet service is too expensive</em></li><li><em>Too slow/frustrating/internet doesn’t work well</em></li><li><em>Service plans from internet provider are confusing</em></li><li><em>Not interested or don’t need/want to use it</em></li><li><em>I don’t know how to use the internet</em></li><li><em>I don’t have a device to access the internet</em></li><li><em>I have no time to learn about it or how to use it</em></li></ul><p>The inability to access information fell disproportionately on low income households. The study showed that 21% of households with incomes under $25K and 10% of households with incomes between $25K and $50K do not have a mobile or smartphone. Certain groups were also more likely to report barriers:</p><ul><li>54% of those living at or below 135% of the Federal Poverty Limit</li><li>49% of Black residents of the city</li><li>38% of older adults (65 years of age or older)</li><li>33% of those living in South Seattle (Council District 2)</li><li>31% of Asian residents of the city</li><li>30% of those who live alone</li></ul><p>Also, “more than one out of ten (13%) residents rely on someone else to help them access or navigate the internet.”</p><p>While most transportation information is delivered via mobile devices, the Access and Adoption Study revealed that, compared to residents who have internet access from multiple devices at home, residents who rely on cell phones to access the internet are:</p><ul><li>more likely to be unemployed and more likely to be disabled</li><li>more likely to live alone</li><li>more likely to live at or below 135% of the Federal Poverty Level (household) and to have lower average (personal) incomes</li><li>more likely to only have a high school level education or some college</li><li>more likely to be a racial or ethnic minority</li></ul><p><strong>The city’s transportation information infrastructure must correct the inequities in information access as part of its efforts to address inequities in transportation access and outcomes.</strong> Lack of access to information directly impacts a household or residents ability to use all the available transportation options in the city and therefore limits their access to opportunities and amenities.</p><h3>…is safe and secure</h3><p>While it’s paramount that users of the transportation system be protected from misuse of their personal information (financial information, origin-destination data, etc.), system users also need protections from issues that stem from how information is managed at the <em>system level</em>. For example, a well-designed <em>geofencing</em> scheme provided to ride-share providers may encourage the drop-off of passengers in safer locations. Similarly, requiring service operators to provide real-time incident and condition information can allow for system-level routing of travelers away from potentially dangerous incidents.</p><p>Providing strategic information to the right system actors at the right time is essential to ensuring these protections now and into the future. In the near term, well-managed information can help us identify safer flight paths for delivery drones, provide real-time asset condition information, and vary speed limits according to current traffic conditions–all of which help improve safety.</p><p>For long-term, inter-generational safety, we need to know what types of information may help protect against threats such as climate change. For example, requiring that system actors provide information on the carbon emissions associated with various travel modes may shift travel behavior to more sustainable modes. Ideally, we will also be able to collect information on near-misses which would allow system managers to identify and target unsafe locations <em>before</em> an incident occurs and build the necessary physical changes to the infrastructure.</p><p>Of course, travelers can also face safety issues if the information system itself fails, whether through malfunction or malicious hacking. For example, a system failure could result in traffic signal outages that may endanger travelers. Municipal DOTs should build redundancy into any transportation information system and should address system security issues at the level of each specific technology.</p><h3>On resilience</h3><p><a href="https://medium.com/u/1c2f1c7efe6">100 Resilient Cities</a> defines a resilient transportation system as:</p><blockquote>“one that promotes safe, equitable, and inclusive accessibility by providing sustainable, integrated, flexible, and robust mobility options — during normal times and times of crisis.” (<em>Attributed to </em><a href="https://www.linkedin.com/in/marianejang/"><em>Mariane Jang</em></a><em>, former Associate Director, Solutions Development &amp; Innovation — Mobility and Urban Development, 100 Resilient Cities)</em></blockquote><p>Information systems, from street signs to online traffic maps, are an essential part of any transportation system. But physical and technological disruptions can cause these systems to function poorly or, in some cases, cause them to cease functioning all together. These failures may undercut safety and equity and exacerbate exclusion (e.g., if a disruption means only travelers with smartphones can navigate the system safely).</p><p>As new technologies are introduced to our aging transportation system, the number and severity of potential disruptions increase exponentially. We should design our information infrastructure to provide for:</p><ul><li>The ability of <strong>DOTs and other system managers</strong> to continue to provide essential information in the face of acute system shocks and chronic stressors, both physical and technological</li><li>The ability of <strong>users of the transportation system</strong> to access transportation information in the face of acute system shocks and chronic stressors, both physical and technological</li></ul><p>To address potential failures, our transportation information infrastructure system should both be flexible and incorporate redundancy, meaning if one information system is unavailable, operations can continue using another. DOTs need to address this with every technology that they considers as they implement the policies, projects, initiatives, and technology investments under this plan.</p><p><em>Up next: </em><strong><em>User stories and requirements for transportation information</em></strong></p><p><em>I drafted this plan with </em><a href="https://medium.com/u/93bd012e5141?source=post_page-----fcf6f27aa185----------------------"><em>Alex Hagenah</em></a><em>, </em><a href="https://medium.com/u/fa908e9a07d1?source=post_page-----fcf6f27aa185----------------------"><em>Sam Marshall</em></a><em>, and </em><a href="https://medium.com/u/9021d9e983b6?source=post_page-----fcf6f27aa185----------------------"><em>Mary Alyce</em></a><em> Eugene, my team mates and former colleagues when I served as the Seattle Department of Transportation’s Chief of Strategy and Innovation. (Our work was shaped by the very helpful insights and inputs from 30+ of our SDOT colleagues.)</em></p><p><em>I have the department’s permission to share the draft plan with whoever asks. Connect with me on </em><a href="https://www.linkedin.com/in/bdelapena"><em>Linked.In</em></a><em> and send me a DM and I will send you a link to the pdf and .docx copies.</em></p><p><em>Feel free to crib, copy, and steal the materials for your city.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=82790bc8ecd5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On Privacy and Equity — managing transportation information]]></title>
            <link>https://medium.com/@benjiedlp/on-privacy-and-equity-managing-transportation-information-cdf9e6635c79?source=rss-f48e59011a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/cdf9e6635c79</guid>
            <category><![CDATA[information]]></category>
            <category><![CDATA[infrastructure]]></category>
            <category><![CDATA[transportation]]></category>
            <category><![CDATA[equity]]></category>
            <category><![CDATA[privacy]]></category>
            <dc:creator><![CDATA[Benjamin de la Pena]]></dc:creator>
            <pubDate>Fri, 20 Dec 2019 16:19:10 GMT</pubDate>
            <atom:updated>2019-12-20T23:37:43.699Z</atom:updated>
            <content:encoded><![CDATA[<h3>On Privacy and Equity — managing transportation information</h3><h4>This is part 14 of a serialized, draft, generic transportation information infrastructure plan meant to help municipal departments of transportation to manage the emerging urban transportation ecosystem</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iLElrtIDTOYY61vWXjpchg.png" /><figcaption>(Graphic by <a href="http://www.xiolugo.com/">Xio Lugo</a> of <a href="https://story2designs.com/">Story2 Designs</a>.)</figcaption></figure><p>Given the history of recent disruptions and innovations and given the structure of the technology stack<strong> every technology project that a municipal department of transportation undertakes should be assessed using the frames of privacy, equity, safety and security, and resiliency. </strong>These frames must apply particularly for systems that push out information to the ecosystem.<strong> </strong>This draft generic plan discuss<strong> </strong>each frame below:</p><h3>On Privacy</h3><p>With more and more data being collected and analyzed about our travel behaviors, it’s becoming increasingly important to “balance the need between gathering information to provide needed services and protecting the public’s privacy.”¹ At no point should travelers, knowingly or otherwise, have their right to privacy threatened or compromised through the release of personally identifiable information. As caretakers and managers of a city’s public right of way, a city DOT has a responsibility to safeguard traveler privacy. The DOT needs to develop policy and regulations around privacy in partnership with both the public and private service providers.</p><p>Most city DOTs are mandated by their local code to collect data essential their mission “to deliver a transpor­tation system that provides safe and affordable access to places and opportunities,” and as data becomes more extensive and precise, the information infrastructure managed by the DOT must value and prioritize traveler privacy to be a trusted, secure public service.²</p><p>In Seattle, policies are currently in effect requiring any proposal for new procurement of data to undergo a privacy assessment, and resources are provided to ensure privacy protections are embedded from the start. Privacy champions in each city department act as liaisons to help staff and spread awareness of privacy issues. Data collection is also guided by the city’s <a href="https://seattlegov.sharepoint.com/sites/itd/privacy/toolkit/SitePages/DemographicandSurveyDataCollection.aspx">Demographic and Survey Data Collection Playbook</a>.</p><p>Any city DOT information technology project should consider the following:</p><ul><li>Ongoing alignment with the <a href="https://seattlegov.sharepoint.com/sites/itd/privacy/toolkit/Shared%20Documents/City%20of%20Seattle%20Privacy%20Principles%20FINAL%20Poster.docx">the city’s Privacy Principles</a> (if any), with <a href="https://seattlegov.sharepoint.com/sites/itd/privacy/toolkit/Shared%20Documents/Privacy%20Policy%20FINAL.docx">policy</a> and prescribed processes</li><li>Alignment with the <a href="http://www.seattle.gov/tech/initiatives/privacy/surveillance-technologies/about-surveillance-ordinance">city’s ordinances around surveillance,</a> if any. (In Seattle, an ordinance regulates the use evaluation, and procurement of technologies that “observe or analyze the movements, behavior, or actions of identifiable individuals in a manner that is reasonably likely to raise concerns about civil liberties, freedom of speech or association, racial equity or social justice.”)</li><li>Policy development, data procurement, and digital infrastructure initiatives guided by users’ privacy needs and underscored by designing proactively for privacy protections.</li><li>Ongoing alignment with transportation agencies; for example:</li><li>The principles set forth by the <a href="https://nacto.org/2019/05/30/managing-mobility-data/">National Association of City Transportation Officials (NACTO)’s Managing Mobility Data</a> policy guidance</li><li>The <a href="https://www.openmobilityfoundation.org/wp-content/uploads/2019/06/OpenMobilityFoundation_Principles.pdf">principles set forth by the Open Mobility Foundation</a> (curators of the MDS)</li><li>National standards for data privacy as proposed by Transportation for America:</li></ul><p>— Compliance with city, state, and federal privacy regulations, standards, and policies especially as it pertains to Washington State’s Public Records Act.</p><p>— The prioritization of data collection from vehicles over users, especially location-based data</p><p>— A clear policy of protecting personally identifiable information from public disclosure without prior aggregation or obfuscation</p><p>— The use of the service is not tied to access to personal data or device</p><p>— Opt-in requirements for access to any element of a user’s device including camera, contacts, or location</p><p>— Operators clearly articulate the data they are collecting from users and explain why they are collecting it</p><p>— A prohibition on the sale of data to third-party entities</p><h4>Special Privacy Considerations</h4><p>Different users may have different privacy needs, and equity is entwined with privacy issues–a relationship that deserves special consideration.</p><p>For example, individuals who are of undocumented immigration status or who have experienced domestic violence may be more vulnerable if certain types of traveler information, such as origin-destination data, are made accessible to the public or discovered through a data breach. People and households with lower incomes are also more at risk of data privacy violations.⁴</p><p>For this reason, we strongly emphasize alignment with the City of Seattle’s privacy principles, particularly Principle 2: “We collect and keep only what we need.” This will help us design systems that support equity in privacy, individual wellbeing, and public benefit. Also, under Executive Order 2016–8 affirming Seattle’s status as a “welcoming city,” city employees will not ask about immigration status.⁵</p><p>— -</p><h3>On Equity</h3><p>In 2005, the City of Seattle became the first city in the nation to adopt a formal framework to address institutional racism — the Seattle Race and Social Justice Initiative (RSJI). In the years since, city departments have adopted RSJI principles and processes, and added supplemental efforts of their own to support equity in ways unique to their work.</p><p>Transportation infrastructure, particularly in U.S., was built without consideration to social justice or equity. Communities of color, minorities, and communities with less resources often bore the brunt of racist and discriminatory policies and investments. In many U.S. cities, transportation has literally embodied <em>structural</em> racism.</p><p>Any DOT investing and rolling out information technology should consider the history of injustice and inequity. DOT managers and leaders should consider three main types of information equity that are critically important to users:</p><ul><li>Transportation information access</li><li>Privacy of transportation user information</li><li>Equitable service outcomes of transportation information use</li></ul><h4>Equitable information access</h4><p>Several factors affect how accessible transportation information is to different demographics. The following is a list of the information access concerns that should be considered when deploying technology:</p><ul><li><strong>Diverse user information needs.</strong> To travel safely and efficiently, transportation system users of different demographics may require different information. For example, a low-income user heading to an overnight shift will likely have very different information needs than a high-income user heading to work during weekday commute hours. In fact, the transportation information needs of any <em>individual</em> user may shift depending on the time of day or day of the week (e.g., commuting to work during the week vs. taking a child to an appointment on a weekend).</li><li><strong>Access to technology.</strong> Travelers increasingly need access to the internet and digital devices to obtain useful, real-time transportation information. In addition to planning for use of internet-delivered information channels, DOTs should plan for the use of information channels that require minimal access to technology. This redundancy of information access not only makes the system more equitable, but also improves resilience in the face of system outage.</li><li><strong>Language.</strong> If providers share information that users need in ways not understandable to the user, because the information is either in an unfamiliar language or at too advanced a reading level, the information is useless to the user. Each DOT technology project should increase language accessibility.</li><li><strong>Physical access.</strong> Hearing impairment, vision impairment, and different forms of neuro-diversity may affect the way some users experience our transportation ecosystem. Technology projects should consider users’ needs, not just in terms of what information they require, but also what<em> </em>accommodations may improve their experience.</li></ul><h4>Equitable service outcomes</h4><p>“Data driven” does not always mean equitable. In fact, in some cases, it can mean the opposite. For example, if transportation service providers optimize their algorithms to maximize profits, some communities may be left under served. Artificial intelligence (AI) and machine learning (ML) algorithms can also perpetuate and exacerbate historical inequities.⁶ This is because AI and ML algorithms are trained on historical data — when historical data reflect biases in our institutions and process, or when training data are selected in a biased way, the biases may be carried over to (but also hidden in) the outputs of predictive algorithms trained on these data.</p><p>DOTs should take a user-needs-first approach to designing and deploying information technology. This means ensuring not only that we provide information to users in an equitable way, but that the <em>outcomes</em> of the way system actors use information are also equitable.</p><p><em>References:</em></p><ol><li><em>From the </em><a href="https://www.seattle.gov/Documents/Departments/InformationTechnology/City-of-Seattle-Privacy-Principles-FINAL.pdf"><em>City of Seattle Privacy Principles</em></a></li></ol><p><a href="http://apps.leg.wa.gov/rcw/default.aspx?cite=42.56"><em>2. The Public Records Act</em></a><em> also makes it difficult to protect data once we have collected it or had it collected on our behalf by a third party.</em></p><p><em>3. See the </em><a href="http://www.seattle.gov/tech/initiatives/privacy/surveillance-technologies"><em>Surveillance Ordinance</em></a><em>.</em></p><p><em>4. Byrne, Ciara. </em><a href="https://www.fastcompany.com/90317495/another-tax-on-the-poor-surrendering-privacy-for-survival"><em>Trading privacy for survival is another tax on the poor</em></a><em>. Fast Company, 18 March 2019.</em></p><p><em>5. Available via: </em><a href="http://murray.seattle.gov/wp-content/uploads/2016/11/Executive-Order-2016-08_Welcoming-City.pdf"><em>http://murray.seattle.gov/wp-content/uploads/2016/11/Executive-Order-2016-08_Welcoming-City.pdf</em></a></p><p><em>6. Angwin, Julia, et. al. “</em><a href="http://www.propublica.org/article/machine-bias-risk-assessments-in-criminal-sentencing"><em>Machine Bias</em></a><em>” ProPublica, 23 May 2016.</em></p><p><em>Up next: </em><strong><em>Making transportation information accessible, safe, and secure</em></strong></p><p><em>I drafted this plan with </em><a href="https://medium.com/u/93bd012e5141?source=post_page-----fcf6f27aa185----------------------"><em>Alex Hagenah</em></a><em>, </em><a href="https://medium.com/u/fa908e9a07d1?source=post_page-----fcf6f27aa185----------------------"><em>Sam Marshall</em></a><em>, and </em><a href="https://medium.com/u/9021d9e983b6?source=post_page-----fcf6f27aa185----------------------"><em>Mary Alyce</em></a><em> Eugene, my team mates and former colleagues when I served as the Seattle Department of Transportation’s Chief of Strategy and Innovation. (Our work was shaped by the very helpful insights and inputs from 30+ of our SDOT colleagues.)</em></p><p><em>I have the department’s permission to share the draft plan with whoever asks. Connect with me on </em><a href="https://www.linkedin.com/in/bdelapena"><em>Linked.In</em></a><em> and send me a DM and I will send you a link to the pdf and .docx copies.</em></p><p><em>Feel free to crib, copy, and steal the materials for your city.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cdf9e6635c79" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Transportation Technology Stack — the technology of location; the technology of disruption]]></title>
            <link>https://medium.com/@benjiedlp/the-transportation-technology-stack-the-technology-of-location-the-technology-of-disruption-c5f81509b13b?source=rss-f48e59011a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/c5f81509b13b</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cities]]></category>
            <category><![CDATA[transportation]]></category>
            <category><![CDATA[infrastructure]]></category>
            <category><![CDATA[information]]></category>
            <dc:creator><![CDATA[Benjamin de la Pena]]></dc:creator>
            <pubDate>Wed, 18 Dec 2019 20:43:44 GMT</pubDate>
            <atom:updated>2019-12-18T20:45:03.618Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong><em>The Transportation Technology Stack — the technology of location; the technology of disruption</em></strong></h3><h4>This is part 13 of a serialized, draft, generic transportation information infrastructure plan meant to help municipal departments of transportation to manage the emerging urban transportation ecosystem</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AQ93HLIesxkm5i8tDa2nPQ.png" /><figcaption>(The transportation technology stack by <a href="http://www.xiolugo.com/">Xio Lugo</a> of <a href="https://story2designs.com/">Story2 Designs</a>.)</figcaption></figure><p>The transportation technology companies’ ability to serve markets across geographies and provide differing transportation options would not be possible without the growth and interoperability of the <em>transportation technology stack</em>.</p><p>The stack provides location information on demand and allows users of city transportation systems to find out where they are, choose where they want to go, and pick a way to get there.</p><p>The stack is not fully integrated and currently traverses several companies, but it is also moving from better interoperability to vertical aggregation.</p><p>The common goal seems to be to make navigation and transacting for urban transportation by any mode as seamless as possible for the user. The question up for grabs is, “Who will own and dominate the stack?” and thereby own the customer and the market.</p><h3>Technology of Location</h3><p>Nearly 20 years ago, Zipcar and Flexcar introduced by-the-hour car sharing to cities in North America. The two companies launched separately in 2000, from separate sides of the continent. The car-sharing services were premised on not needing to own a car, because you can have “wheels when you want them.”¹</p><p>Car-sharing’s implied promise of not needing to own a car (or at least a second car) was probably the first major step in the disruption of the then existing paradigm of urban transportation. Either you owned a car (or rented a car) or you took public transportation. Short-term car-sharing provided a new option. Zipcar and Flexcar were also the harbingers of how innovations in information technology would drive radical changes in mobility.</p><p>The idea of car-sharing and short-term car rental was not new² but where older models had come and gone, Zipcar and Flexcar found a path to growth and rapid adoption. They found a path by deploying digital technologies that were, at the time, just becoming ubiquitous: the web via the mobile internet.</p><p>What powered each service was a digitized online map and devices that could share a precise enough location on that map. This allowed customers to find and book the cars nearest to them. The business model was enabled by radical changes in how information was received, processed, and delivered.</p><p>The web, delivered faster via cable internet (no more dial-up) –and later by cell networks, allowed car-share members to select and book cars on short notice and with no paperwork. Radio transceivers and wireless data links allowed the companies to send commands remotely — for example, to verify radio-frequency ID (RFID)-equipped³ membership cards and to unlock or even turn off the car. Text messaging (or SMS) provided two-way communication without need of an intermediary. The company could notify the member, and the member could extend reservations or log complaints over SMS.</p><p>Alongside these technologies grew:</p><ul><li>the mobile internet⁴;</li><li>commercial global positioning system (GPS) services;</li><li>digital geographic information systems (GIS);</li><li>smartphones;</li><li>web-based maps;</li><li>app ecosystems;</li><li>mobile payment gateways;</li><li>RFIDs and near-field communications;</li><li>general transit feed specification (GTFS)⁵; and,</li><li>a host of other mobile and location technologies.⁶</li></ul><p>These innovations transformed transportation through layers of information services that were as important, if not more so, than the physical vehicles that conveyed the service. Technology upended the traditional models of vehicle ownership, and afforded users more travel choices that fit their needs and lifestyles.</p><p>In the years since the two car-sharing companies launched, more new services were built on these technologies and more new companies emerged. Each new entrant sought to change the way people got around the city. Because these new services did not quite fit into existing regulatory categories, most cities were caught unawares as new mobility offerings just showed up on the streets.</p><p>As each new service arrived, municipal departments of transportation scrambled to make rules. Cities tried outright bans or created new permits, new regulations, new fees. None of these efforts came easily. Each was debated and contested. What was clear though was the blistering pace of adoption. People took to these new services. Cities were forced to adapt.</p><p>The new services were not without upsides for cities. There was the promise of reducing private vehicle use and maybe congestion. The underlying location-based information technology also held out the potential of providing insights on how vehicles and people moved across the city — a degree of granularity previously unavailable for transportation planning or traffic management purposes. So there were new debates around access to mobility data. Cities soon began requiring access to the information in return for permission to operate on the streets. All of this is still being litigated.</p><p>This year, a consortium of city transportation agencies, led by Los Angeles DOT, developed the mobility data specification (MDS). The specification is</p><blockquote>“comprised of a set of Application Programming Interfaces (APIs) that create standard communications between cities and private companies to improve their operations. The APIs allow cities to access data that can inform real-time traffic management and public policy decisions to enhance safety, equity, and quality of life.”</blockquote><p>The consortium of cities also formed the Open Mobility Foundation (OMF), “an open-source software foundation that creates a governance structure around open-source mobility tools, beginning with a focus on the Mobility Data Specification (MDS).”</p><p>OMF and the MDS could just be the next salvo in the running battle to regulate the urban transportation network through information. Two decades since the advent of web-enabled car-sharing, continuing innovations in technology (with the rapid developments in machine learning and artificial intelligence) promise even more innovation and disruption in urban mobility. And even more battles around data access, ethics, privacy, surveillance, and equity.</p><h3>Technology and Disruption</h3><p>If the year 2000 was the birth year of new mobility disruption, the year 2007 was the year of the growth spurt. The iPhone, the App Store, Google Maps, and Open Street Map all launched in 2007. The mobile web on iOS and then Android OS⁷, powered by apps, made car-sharing even more convenient and memberships skyrocketed.⁸</p><p>In 2007, Paris also launched <em>Vélib’</em>, a 6,000-unit public bike-share system. The service was run as a concession funded by advertising. Other cities would soon copy the service and the business model and docked bike-share systems soon became a feature of most large American cities. Each city’s service was also funded either by private advertising or through public-private partnerships.</p><p>The pace of change also accelerated in the business space. Just seven years after their launch, Zipcar swallowed up Flexcar. Later, Avis would buy up Zipcar while the other incumbents in the car-rental market launched their own short-term car rental services with varying success.</p><p>The years 2012 and 2013 saw the launch of new ride-hail services Uber and Lyft⁹. Taxi and limousine services lost ground and taxi-medallions (the permit to operate a taxi) lost value. In New York City, the price dropped from a high of $1,000,000 per medallion in 2013, to just $650,000 in 2015¹⁰.</p><p>In 2016, app-enabled dockless bike-shares began showing up on city streets. A myriad companies, the largest ones coming from China, appeared seemingly overnight and deployed millions of bikes across cities in North America and the rest of the world¹¹. Two years later, startups like Bird introduced shared electric kick scooters (a.k.a. e-scooters) to city streets.</p><p>Meanwhile, Google’s Self-Driving Car Project¹² (a.k.a. autonomous vehicles or “AV”) — which it launched in 2009 — also began testing autonomous vehicles directly on city streets, often in partnership with local and state governments. Other companies would soon follow suit. (While the hype is waning, the numbers of AVs on the road and the services that provide them will likely only grow in the coming years.¹³)</p><p>This year, established aviation companies like Boeing and Airbus, alongside ambitious startups, began testing urban air transport via passenger carrying unmanned drones, i.e. “flying AV taxis.” Clearly they see potential. One study estimated that there was a global market worth $318B that will grow between now and 2040.¹⁴)</p><p>Drone deliveries, by land or air, have also debuted on city streets. This is on top of the explosive growth of urban goods deliveries, driven by online commerce sales paired with same-day or next day delivery service. Delivery companies are contemplating combining autonomous road vehicles with legged robots for doorstop drop-offs.</p><p>The market also continues to consolidate and the game continues to change. The private-sector actors¹⁵ moved beyond their starting modes and are working to insert themselves at every transportation choice a user makes. Uber and Lyft have grown rapidly as ride-hail companies but each has acquired bike-share companies and rolled out e-scooters. On the promise of more growth, they raised more than a combined $10 billion when they launched their initial public offerings.</p><p>Bird, the company that introduced kick e-scooter services, is rolling out a seated scooter that looks very much like a pedal-less e-bike. Lime, which started as a dockless bike-share service expanded into e-scooters and now offers car sharing. Meanwhile, many of the original dockless bike share players like Mobo and oFo have folded and left the market.</p><p>All the private actors are now engaging public transportation and negotiating service deals (where on-demand service replaces low-volume transit routes) and/or payment options through their apps. Uber’s CEO declared that the company wants to be the “Amazon of transportation,”¹⁶ referring to the market dominance of the online retailer.</p><p>But the risks of company and market failure are also growing. In August of 2019, Uber reported a net loss of $5.2 B just for that quarter. Lyft lost $644 M in the same period¹⁷. ReachNow, a car-sharing company, abruptly shut down when it’s owner, BMW Group, entered into a new mobility joint venture with Daimler Benz that owned Car2Go.</p><p>Reports said, “The closure was so abrupt, ReachNow included instructions for customers [in the middle of] driving one of their free-floating BMWs at the time they received the email.</p><p>‘If you are in an active rental, do not fear,’ the email said. ‘Please end your trip in the coverage area as normal when you are done.’”¹⁸</p><p>As in any disruption, the ground shifts underneath and the system becomes fragile, leaving travelers in the lurch.</p><p><em>References:</em></p><p><em>1. “Car sharing’s time comes.” CNN Money, July 19, 2000.</em></p><p><em>2. There were exclusive car clubs starting back in the 1940s and there were several car-share services operating in Europe.</em></p><p><em>3. RFID technology allows information to be stored digitally in miniature “tags” that can be captured by an electronic reader.</em></p><p><em>4. Brian McCullough. “How the Internet Happened: From Netscape to the iPhone.” (New York: Livewright/Norton, 2018.)</em></p><p><em>5. General Transit Feed Specification is a common data format for digital sharing of public transportation schedules and associated geographic information</em></p><p><em>6. Rampton, John. “</em><a href="http://techcrunch.com/2016/06/17/the-evolution-of-the-mobile-payment/"><em>The Evolution of the Mobile Payment</em></a><em>.” Techcrunch, 17 June 2016, 7:00 AM,</em></p><p><em>7. As well as the competing mobile OS platforms from Windows, Nokia, and a host of other companies</em></p><p><em>8. In the US, car-share memberships grew from 200,000 in 2007 to nearly a million by 2012, just five years later.</em></p><p><em>9. S. Shaheen, N. Chan, A. Bansal, and A. Cohen, “Definitions, Industry Developments, and Early Understanding.” Shared Mobility: A Sustainability &amp; Technologies Workshop. Transportation Sustainability Research Center, University of California Berkeley, November 2015.</em></p><p><em>10. By 2018, the price would drop to $200,000. (See “</em><a href="https://www.npr.org/sections/money/2018/05/23/613776997/episode-643-the-taxi-king"><em>Episode 643: The Taxi King</em></a><em>.”) Planet Money, NPR, 23 May 2018.</em></p><p><em>11. “</em><a href="https://www.wsj.com/articles/chinese-startups-saddle-up-for-bike-sharing-battle-1477392508"><em>Chinese Startups Saddle Up for Bike-Sharing Battle</em></a><em>.” Wall Street Journal, 25 October 2016.</em></p><p><em>12. Now called Waymo.</em></p><p><em>13. One prediction says human drivers will be prohibited from roads by 2040 </em><a href="http://www.dot.state.mn.us/research/TS/2016/201602.pdf"><em>http://www.dot.state.mn.us/research/TS/2016/201602.pdf</em></a></p><p><em>14. Garrett-Glaser, Brian. “Will the Global Urban Air Mobility Market Justify the Investment?” Avionics Today, 22 August 2019. Retrieved via </em><a href="https://www.aviationtoday.com/2019/08/22/will-global-urban-air-mobility-market-justify-investment/"><em>https://www.aviationtoday.com/2019/08/22/will-global-urban-air-mobility-market-justify-investment/</em></a></p><p><em>15. Outside the names known in the U.S. are the operators emerging in China (Didi Chuxing), South East Asia (Grab and GoJek), Latin America (99), North Africa (Careem), South Africa (Taxify), India (Ola), and others.</em></p><p><em>16. </em><a href="https://phys.org/news/2019-03-ipo-due-uber-aims-amazon.html"><em>https://phys.org/news/2019-03-ipo-due-uber-aims-amazon.html</em></a></p><p><em>17. ‘</em><a href="https://www.theverge.com/2019/8/8/20793793/uber-5-billion-quarter-loss-profit-lyft-traffic-2019"><em>Uber lost over $5 billion in one quarter, but don’t worry, it gets worse.</em></a><em>” By Andrew J. Hawkins</em></p><p><em>18. Nickelsburg, Monica. Inside the abrupt shutdown of BMW’s ReachNow car-sharing service in Seattle and Portland. Geekwire, 5 August 2019. Retrieved from </em><a href="https://www.geekwire.com/2019/inside-abrupt-shutdown-bmws-reachnow-car-sharing-service-seattle-portland/"><em>https://www.geekwire.com/2019/inside-abrupt-shutdown-bmws-reachnow-car-sharing-service-seattle-portland/</em></a></p><p><em>Up next: </em><strong><em>Further frames for transportation information infrastructure</em></strong></p><p><em>I drafted this plan with </em><a href="https://medium.com/u/93bd012e5141?source=post_page-----fcf6f27aa185----------------------"><em>Alex Hagenah</em></a><em>, </em><a href="https://medium.com/u/fa908e9a07d1?source=post_page-----fcf6f27aa185----------------------"><em>Sam Marshall</em></a><em>, and </em><a href="https://medium.com/u/9021d9e983b6?source=post_page-----fcf6f27aa185----------------------"><em>Mary Alyce</em></a><em> Eugene, my team mates and former colleagues when I served as the Seattle Department of Transportation’s Chief of Strategy and Innovation. (Our work was shaped by the very helpful insights and inputs from 30+ of our SDOT colleagues.)</em></p><p><em>I have the department’s permission to share the draft plan with whoever asks. Connect with me on </em><a href="https://www.linkedin.com/in/bdelapena"><em>Linked.In</em></a><em> and send me a DM and I will send you a link to the pdf and .docx copies.</em></p><p><em>Feel free to crib, copy, and steal the materials for your city.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c5f81509b13b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>