1. Designing your local technology stack
Thomas Craig, General Manager

2. Your transit system is made up of technologies
Your transit system is made up of technologies. - Buses - Bus stops - Schedules - Left/Right sheets - Board of Directors meeting agenda templates

3. You are a technology expert.
In this section:
Best-practices conforming GTFS
OpenStreetMap
On the horizon: GTFS-flex
No matter what software you use—the data must be open and in a standardized format
All data requires maintenance
TNexT

4. Technologies are just tools and processes
A group of technologies connected together is a technology stack.
Your agency is a transit technology stack.

5. Step 1: Define the parts

6. Technology is made up of components. Defined forms, defined purposes.

7. A single component might have multiple forms, and might have multiple purposes.

8. But each form and purpose is discrete and can (should
But each form and purpose is discrete and can (should?) be defined separately.

9. Example Your website is a component.
It has subcomponents in software, hardware, and data forms.
It has subcomponents that serve information, operations, and planning purposes.

10. Example Procuring your website, those subcomponents must be defined:
The trip planner widget (software) directs users to transit directions (information).
The web server (hardware) ensures the website can be reached (operations).
The board meeting posts (data) are stored for retrieval and use by agency (planning).

11. Core application - GTFS
GTFS data is one of the most important components of any fixed route technology stack.
GTFS is data, and its primary purpose is information.
But GTFS also has planning and operations applications, and many subcomponents!

12. Core application - GTFS

13. Core application - GTFS

14. Other Examples? Runcutting system Print Schedules System Map
On board GPS
GTFS
Prediction Engine
Website

15. Step 2: Connect them together

16. Every component affects others
Runcutting system
Print Schedules
System Map
On board GPS
GTFS
Prediction Engine
Website

17. Each component’s purpose relies upon interactions with other components.

18. Software is no good without data and hardware.
Operations is no good without planning and information.

19. Example Your GTFS data doesn’t trip plan by itself.
Google Maps is the software that identifies the best routing.
Your riders’ iPhone or Android hardware is the screen through which riders will see that information.

20. Example
(Yes that’s right—Google Maps and every cell phone in your service area is part of your
transit technology stack.)

21. Example (to be a bit more endogenous)
Your stop inventory data doesn’t update itself.
ESRI Collector software allows your facilities maintenance team to update locations, amenity information.
And that team needs smartphone or table hardware to run that software.

22. So you want a new website…
Your website has information, operations, planning components, and absolutely nothing on it should have to be recreated from scratch.
So the first step to procuring a website is not to define the technical specifications. Rather, the first step is to define the end uses.

23. So you want a new website…
From those use cases you want your website to support, you identify which components you already have.
And your technical specifications are then mostly integrations, rather than the creation of new features.

24. Step 3: Don’t break the system

25. Keep the system working.
Right now you have a working system.
You have a whole lot of really important jobs.
But the most important job is clear:
Replace screenshots with Vermont agency/agencies?
Keep the system working.

26. Replacing everything at once is a great way to break everything.

27. How do we change operators?
It’s tough. We wouldn’t do the whole system at once if we could avoid it. But at very least we are REALLY careful about it.

28. One step at a time, if we could.
It’s tough. We wouldn’t do the whole system at once if we could avoid it. But at very least we are REALLY careful about it.

29. Every component affects others
Runcutting system
Print Schedules
System Map
On board GPS
GTFS
Prediction Engine
Website

30. If you just change the system map, there’s just two connections to fix
If you just change the system map, there’s just two connections to fix. System map, GTFS, and website?
Runcutting system
Print Schedules
System Map
On board GPS
GTFS
Prediction Engine
Website

31. Data makes the simplest, best connections.
Data is special.
Data makes the simplest, best connections.

32. that purpose if it is standardized.
But data can only serve
that purpose if it is standardized.

33. Application-centric design
Leaving this in here just bc I think I should find a place for it.

34. Standards-centric design
Leaving this in here just bc I think I should find a place for it.

35. Back to Step 1: Define your
Transit Stack

36. A “technology stack” is a group of components connected for to create a working system.

37. Your transit agency has a technology stack, too.

38. Don’t procure an Intelligent Transportation System You are an intelligent transportation system.

39. Define the components. Connect them together.
Don’t break it; improve it.

40. Designing your local technology stack
Thomas Craig
General Manager
ext. 4